I would like to add issues, that have nothing in common, to a view that only I can see.
With other Management Tools, I could drag the issue into a bucket and it would create a shortcut to the original. If dragging is complicated, use a star, heart, binocular icon to create a private list.
I do not want to use labels. No one else on the Project needs to see that additional information on the Jira. We are already using Label to track a multitude of things.
I do not want to use watch list. The issues I need to follow don't involve me, but I want to follow up to see the out come of any policy changes.
Flags are shared with everyone, so that is not an option.
Hi @Suzy , like you I've wanted to be able add issues to my personal favorites list without, for example, polluting the global label space or piggy backing on the watchers feature.
We created a Jira Cloud app that allows you to add Issues to your own personal favorites list. Favorites are scoped to individual user accounts, so everyone on your team can favorite issues independently:
You can even create multiple personal favorites lists to further categorize Issues that are relevant to you. You can also search for issues that you've assigned to your personal custom favorites lists using JQL.
The app is called Issue Star, and you can find it here: https://marketplace.atlassian.com/1234079
Try the app out, and let us know what you think. Thanks!
There was a plugin named "Favourite Issues" (by Spartez) which did what I think you want, but it was discontinued for the newer Jira versions. You might want to follow any further discussions in https://jira.atlassian.com/browse/JRASERVER-20224 too. I don't have any actual answers, though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It appear that creating an Favorite List was a request, then solved by a 3rd party plug in, then the plug in removed.
How do I either reopen the original request or create a request that can be voted on?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can create a new issue in that Jira, but I'm assuming they'd only close it as being a duplicate on JRASERVER-20224. (At least that's what I'd do.) Keep on commenting the original request until Atlassian (or some plugin maker seeing a market option; might be more hope for that?) see the need.
(https://community.atlassian.com/t5/Jira-articles/An-updated-workflow-for-Server-feature-suggestions/ba-p/721632, from this February, has some description of how to suggest features and how Atlassian reviews them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Suzy,
you are going to need 'some' field to 'favorite' an issue. So if not labels, flags or watch then you would need to consider adding a field, e.g. a checkbox for this purpose. You could hide it from all others if you want. You might search addons if that doesn't work for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not an administrator, I am a user. I am trying to solve for every member on my team - about 20. This is another reason I cannot use labels. We are using labels for pertinent information. I can't have people putting in random customized labels because it will cause too much clutter.
If I understand your steps:
I will be happy to use a checkbox or flag. Please detail how I use this so my entire team can choose which items to watch without seeing each others items when they filter.
"Favorites" is a pretty basic feature for many products. It seems like all of Atlassian customers would benefit from it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Suzy, no for sure don't do #1. that would be much worse than label clutter in the end. :-) I originally assumed this was simply something you wanted for yourself but if you want to expand to others then we need to discuss further...
The idea of a single custom field ("Favorite") would still work based on the new requirements (all users) IF the following assumption can be made. My favorites list will consist of issues that are either assigned to me OR I am watching. If so then I can easily create a jql - Favorite = True AND (assigned = currentuser() OR watcher = currentuser())
Now with that said, I would argue that you could accomplish the same thing with the Flag feature so you might want to reconsider.
Again, this makes a big assumption that if you are going to favorite an issue then you are either assigned or watching. However, I would contend that if it is my favorite then one of those two should be the case.
Other than that you can search the Marketplace for addons but I don't know of any right off.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.