[#JRA-8356] Bookmark issues for easy reference.

JIRA

Bookmark issues for easy reference.

Created: 27/Oct/05 03:47 PM Updated: 02/Jan/08 09:43 PM

Component/s:

Extensions

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-7068 Allow for list of issues to be saved as a filter

Participants:	Anton Mazkovoi [Atlassian] and Kevin Wilson
Since last comment:	2 years, 49 weeks, 4 days ago
Labels:

Description

« Hide

It would be quite handy to be able to bookmark an issue and store it under a user defined tree structure to easily categorize issues, etc. Many issue that get resolved have some good howto/what was info in them that you would like to pull up on a moments notice in order to use the 'fix' contained therein.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 27/Oct/05 06:45 PM

Kevin,

When we implement JRA-7068 will this meet your needs for this issue as well? Or do you strictly need a hierarchy? A hierarchy would probably be more difficult to achieve.

Anton

[ Permlink | « Hide ]

Kevin Wilson added a comment - 28/Oct/05 10:40 AM

I guess for the first go around a link along side watch/vote that simply says bookmark would do the trick with the hierarchal storing ability coming later once you guys change the project structure so it can be stored in a tree instead of a list. you could then just extend that structure to be used for the bookmark cataloging.

[ Permlink | « Hide ]

Kevin Wilson added a comment - 28/Oct/05 10:45 AM

I didn't answer your question directly I guess --> "When we implement JRA-7068 will this meet your needs for this issue as well?"

Maybe, I'll try it out once you release it and see if it quick to do (user friendly wise) and report back.

[ Permlink | « Hide ]

Kevin Wilson added a comment - 28/Oct/05 02:34 PM

Any chance JRA-7068 will be in 3.4.0 or 3.4.1?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 30/Oct/05 04:59 PM

Kevin,

We are trying to implement a usable workaround for JIRA-7068. The workaround will be a custom field which is described in JRA-7068 by Nick. Hopefully, it will be enough to get you going.

Anton

[ Permlink | « Hide ]

Kevin Wilson added a comment - 31/Oct/05 08:55 AM

Oh yeah, I heard about that. Yeah, what Nick (and you) describe in 7068 should do the trick.