How are people managing unranked / unevaluated feature requests within Jira? For example, if one of my co-workers has an idea I want them to be able to easily log it within JIRA but I don't want it silently falling to to the bottom of my backlog, or worse, starting at the top.
In Pivotal tracker, this feature is called the icebox, thus the post tile.
Depends on the process. If it's proper scrum, then it goes into the backlog, and then your workers emphasise its importance during planning. I tend to stick labels on them so people can quickly find them during planning.
Or you could build it into the workflow and have an explicit icebox status.
But if you add issues faster than you finish them, it's only a matter of time until your backlog is larger than you can manage it.
Then the new issues either go to the bottom of the backlog and are easily forgotten, or they go to the top of the backlog and keep frustrating your previous planning work.
The asker is looking for a way to manage this by having a bag for unranked stories where new ones can be automatically dumped without disturbing the cataloguing and planning work that has been done on the backlog with the ranked and prioritized stories.
I think your answer does not address that.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG