-
Suggestion
-
Resolution: Duplicate
-
1
-
Our work items may have different "weight" depending on the column they're in. For example, we have a work item type that is very easy for development (1/10 the dev work that other items are) but is the same work for QA and Operations as other work items. We've found the best way to do that is to be able to configure the column constraints differently for each column, based on a separate field (such as Story Points, or Work Item Weight, or whatever). So we want to configure one column for a constraint of 3 "Work Item Weights" but the next column for a constraint of 5 items. We can do this today in that old fashioned task board, but were disappointed to find it unavailable in the newfangled Rapid Board. We're stuck using both, for different things (sigh).
- derived from
-
- Gathering Interest
- duplicates
-
- Gathering Interest
- has a derivative of
-
- Closed
- incorporates
-
- Future Consideration
- is related to
-
- Closed
-
- Closed
- relates to
-
- Closed
[JSWCLOUD-4010] Ability to set column constraints separately for each column (and by other fields, not just item count)
The product has changed since this ticket was first created. It is now possible to set different column constraints for different columns:
For the second part of this suggestion, there is another ticket with slightly more votes that asks for more column constraints field types: JSWCLOUD-4917 – Allow Column Constraint to be set to any numeric field (i.e Story Points)
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I will close this ticket now.
All comments
The product has changed since this ticket was first created. It is now possible to set different column constraints for different columns:
For the second part of this suggestion, there is another ticket with slightly more votes that asks for more column constraints field types: JSWCLOUD-4917 – Allow Column Constraint to be set to any numeric field (i.e Story Points)
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I will close this ticket now.
Stephan Janssen
added a comment - Since more teams are switching to rapid boards this feature request has come up. It would be of great use for scrum boards.
Stephan Janssen
added a comment - Since more teams are switching to rapid boards this feature request has come up. It would be of great use for scrum boards. 
André R.
added a comment - Feature request about adding an option for "Issue count excluding Sub-Tasks" can be found here: https://jira.atlassian.com/browse/GHS-3772
André R.
added a comment - Feature request about adding an option for "Issue count excluding Sub-Tasks" can be found here: https://jira.atlassian.com/browse/GHS-3772 
After some analysis, we've found that this ticket is a duplicate of the request JSWCLOUD-4917 – Allow Column Constraint to be set to any numeric field (i.e Story Points) which has more votes.
We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.