488942 - The term "bookmarkable template" is meaningless to new users, change to "Make Template"

Status: RESOLVED FIXED

(Bugzilla :: User Interface, defect)

Description

[Max Kanat-Alexander]

Pyrzak's students' research pointed out that the term "bookmarkable template" doesn't mean anything to most people, and so they won't use it. I have no idea what to rename it, but we should probably give it some clearer name.

Comment 1

[Max Kanat-Alexander]

The helpwanted is that we need some good suggestions for how to re-work that button so that it's sensible to people who don't already know what it is.

Comment 2

[Frédéric Buclin]

"Save entered values to your bookmarks"?

Comment 3

[Guy Pyrzak]

I actually think of this as creating a perma-link to this but that isn't quite right either, because it takes you to a page with a perma-link on it.

The problems it doesn't add it to your bookmarks, it takes you to some other page which shows you a lick which if you then right click on and say "add to bookmarks" it will add it to your bookmarks. This is actually one of the MOST confusing things the our testers and we had to explain it over and over.

Anyway, the page that it takes you to, has a perma-link of the template. Which is kinda what blogs do with blog postings, IMO.

Comment 4

[Teemu Mannermaa (:wicked)]

My first thought was that should we add JS to actually add a bookmark instead of showing this intermediate page? Is there any other use case for this link or is bookmark the only one? I would think there are many ways this link gets passed around (email, IM, intranet) so calling it "bookmark" could be wrong.

Something similar to term perma-link would probably be fine. Is that really what these things are called in the web?

What's the most thing people do with this link? Could we keep it updated right there on the same page with JS so users can just right-click and have their browser provide options to copy/bookmark etc.

Comment 5

[Max Kanat-Alexander]

(In reply to comment #4)
> My first thought was that should we add JS to actually add a bookmark instead
> of showing this intermediate page? 

  Yeah, I like that idea, if it can be done.

> Is there any other use case for this link or
> is bookmark the only one? I would think there are many ways this link gets
> passed around (email, IM, intranet) so calling it "bookmark" could be wrong.

  Oh, that's a good point, actually. Yeah, people might use the URL for "file a bug in our product" or something like that.

> Something similar to term perma-link would probably be fine. Is that really
> what these things are called in the web?

  No, permalink usually means "a link to this page that doesn't change", not really "a link to a pre-filled form".

> What's the most thing people do with this link? 

  No idea. I've only used it once, and I used it for a bookmark.

Comment 6

[Dan Wierenga]

(In reply to comment #5)
> (In reply to comment #4)
> > What's the most thing people do with this link? 
> 
>   No idea. I've only used it once, and I used it for a bookmark.

My $0.02:  I'm not convinced there's a huge use-case for new users.  But, I do agree that "Remember values as a bookmarkable template" is a hideous phrase to lay on someone who's not 100% sure what that button does.  I've only ever seen it used by power users, in two different flavors. 

One group of power users are QA people who want a bookmark because they're likely going to be entering a whole bunch of defects on the same product.

The other group of power users use it to make a "here's a shortcut to create similar bugs" or "here's a shortcut to create an appropriate bug for this product" link to send to naive users. 

I've heard these called "canned bug entries", though I can't think of a succinct way of expressing that in a button/link that doesn't feel clumsy. I've also heard it said many times that Bugzilla should save these links for you, just like Saved Searches.  Creating a link that the user has to manually bookmark is just really odd when the user is a logged-in Bugzilla user. 

How about something like "Make a shortcut for more bugs like this" as a link instead of a button, with a rather verbose tooltip?

Comment 7

[Eric Black]

Our company uses the bookmark links extensively for creating links to pre-filled forms for non-technical users which are posted on a internal wiki page with a description of what the form is for, as well as what Dan W. said in comment #6 about power users.

I'm surveying the 30 or so technical users in my company for what they think would be better. If I get any good feedback, I'll post it.

I have a feeling that it will be difficult to create a short descriptive name that will describe it's functionality well enough for new users and still fit on a button.

Comment 8

[Eric Black]

(In reply to comment #7)
> I'm surveying the 30 or so technical users in my company for what they think
> would be better. If I get any good feedback, I'll post it.

Well, I didn't get much of a response, the only two worthwhile being:

Create Template Link
Create Pre-Filled Bug Template URL

Comment 9

[Max Kanat-Alexander]

"Link to Pre-Filed Form" is probably most descriptive, but also possibly confusing.

Comment 10

[Frédéric Buclin]

Bugzilla 3.6 is now restricted to security fixes only, and this bug got no traction for several months. We will retarget this bug once it has a patch ready for checkin.

Comment 11

[Matt Selsky [:selsky]]

Attachment: v1

Comment 12

[Gervase Markham [:gerv]]

Comment on attachment 8536130 [details] [diff] [review]
v1

Review of attachment 8536130 [details] [diff] [review]:
-----------------------------------------------------------------

Matt, I think you've got beyond "good first bug"s now :-) Don't hoover them all up so there's none left, OK? :-)

Gerv

::: template/en/default/bug/create/create.html.tmpl
@@ +615,4 @@
>        <input type="submit" id="commit" value="Submit [% terms.Bug %]">
>        &nbsp;&nbsp;&nbsp;&nbsp;
>        <input type="submit" name="maketemplate" id="maketemplate"
> +             value="Link to Pre-Filed Form"

It's spelt "pre-filled". But I think the best text which balances explanatoriness (is that a word?) and shortness would have the bottom of the form looking like this:

[Submit Bug] or [Make Template] (useful for filing several similar bugs)

where "Make Template" is the button text and the other text is next door. Then, on the target page, we fix the explanation there to read:

If you bookmark or right-click <a>this link</a>, and open it repeatedly in a new window, you can bring up multiple copies of the Enter Bug page with the fields initialized in the way you just had them completed. You can then customise each one as necessary.


Gerv

Comment 13

[Joel Maher ( :jmaher ) (UTC -8)]

just driving by here, I see there is a r- a few weeks ago.  Matt, do you need further information to address the review comments?

Comment 14

[Matt Selsky [:selsky]]

Attachment: v2

Just needed some time to get back to this.  Let me know if the text next to the "Make Template" button should instead be a tooltip.

Comment 15

[Gervase Markham [:gerv]]

Comment on attachment 8555655 [details] [diff] [review]
v2

Review of attachment 8555655 [details] [diff] [review]:
-----------------------------------------------------------------

r=gerv.

Gerv

Comment 16

[Frédéric Buclin]

The bug summary doesn't match what the patch really does. Confusing!

Comment 17

[Gervase Markham [:gerv]]

To ssh://[e-mail]/bugzilla/bugzilla.git
   b8575ad..bc69ce1  master -> master

(With one tiny wording change)

Thanks, Matt!

Gerv

Comment 18

[Andre Klapper]

Could that be backported to 5.0 (or does something not allow string changes)?

Comment 19

[Frédéric Buclin]

Comment on attachment 8555655 [details] [diff] [review]
v2

>+++ b/template/en/default/bug/create/make-template.html.tmpl

> [%# INTERFACE:
>   # url: URL to a pre-filled bug entry form.
>-  # short_desc: Bug summary as entered in the form.
>   #%]

This patch is incomplete. As you don't need short_desc anymore, you shouldn't define it in post_bug.cgi either.

Comment 20

[Frédéric Buclin]

Attachment: post_bug.cgi fix

I committed this fix.

To ssh://[e-mail]/bugzilla/bugzilla.git
   bc69ce1..c104aa5  master -> master

Comment 21

[Gervase Markham [:gerv]]

(In reply to Andre Klapper from comment #18)
> Could that be backported to 5.0 (or does something not allow string changes)?

5.0 is frozen; feel free to backport to your local install :-)

Gerv

Comment 22

[Andre Klapper]

(In reply to Gervase Markham [:gerv] from comment #21)
> 5.0 is frozen; feel free to backport to your local install :-)

Ah, well I didn't mean 5.0.0 but 5.0.x. If 5.0.x is not string-frozen. :)

Comment 23

[David Lawrence [:dkl]]

(In reply to Andre Klapper from comment #22)
> (In reply to Gervase Markham [:gerv] from comment #21)
> > 5.0 is frozen; feel free to backport to your local install :-)
> 
> Ah, well I didn't mean 5.0.0 but 5.0.x. If 5.0.x is not string-frozen. :)

As I understand it, we agreed that there will not be a 5.0.x or 5.x unless there is a security fix needed. The next release will be 6.0 (hopefully 6 months after 5.0 is released).

dkl