-
Suggestion
-
Resolution: Duplicate
-
None
Some customers want new issues that are raised to appear at the top of the planning board, currently to achieve this you have to select the top-most bug so when a new card is created it appears above the highlighted bug.
It should be possible to have a default rank set so new cards will appear at that rank automatically. Currently people are trying (understandably) to edit the default value of the Rank custom field (GHS-2312, GHS-2590) but it throws a stack trace (or did up until GH 5.4 anyway). A separate option within GreenHopper's settings to configure this would be great.
- duplicates
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-2741] Ability to choose default rank for new bugs
Chris Price
added a comment - Dear Nicholas,
It appears to me that you marked this issue as a dupe of a different issue which had already been closed. It doesn't seem like it would help much to add ourselves as watchers on that issue... do you have any other suggestions? Would you consider re-opening one of the two?
Chris Price
added a comment - Dear Nicholas,
It appears to me that you marked this issue as a dupe of a different issue which had already been closed. It doesn't seem like it would help much to add ourselves as watchers on that issue... do you have any other suggestions? Would you consider re-opening one of the two? 
Nicholas Muldoon [Atlassian]
added a comment - Hi,
I am closing this issue as a duplicate of GHS-749. Please view/vote/watch that issue instead.
Thank you.
Nicholas Muldoon
Nicholas Muldoon [Atlassian]
added a comment - Hi,
I am closing this issue as a duplicate of GHS-749 . Please view/vote/watch that issue instead.
Thank you.
Nicholas Muldoon Nicholas Muldoon [Atlassian]
added a comment - Linking this issue to a previously created issue which covers the same functionality.
Nicholas Muldoon [Atlassian]
added a comment - Linking this issue to a previously created issue which covers the same functionality. 
John Lammers
added a comment - This would be handy. Currently, we are always manually moving bugs to the top of the list.
BTW, putting bugs automatically to the top of the Sprint Backlog and the Product Backlog are standard rules in Scrum, at least the way I was taught. It helps us maintain our products in a totally bug free state at all times (and avoid Broken Window Syndrome).
--John Lammers, BMath, CSM.
John Lammers
added a comment - This would be handy. Currently, we are always manually moving bugs to the top of the list.
BTW, putting bugs automatically to the top of the Sprint Backlog and the Product Backlog are standard rules in Scrum, at least the way I was taught. It helps us maintain our products in a totally bug free state at all times (and avoid Broken Window Syndrome).
--John Lammers, BMath, CSM. 
Mark Connolly
added a comment - More specifically, I only want new Bugs to appear at the top of a Greenhopper list, as bugs are almost always a higher priority than an existing Story on our team. Having said that, having all issues appear at the top would be ok.
Mark Connolly
added a comment - More specifically, I only want new Bugs to appear at the top of a Greenhopper list, as bugs are almost always a higher priority than an existing Story on our team. Having said that, having all issues appear at the top would be ok.
Apologies John, GHS-749 reopened.