I work in a wider product team with around 8 delivery teams. I have added a tag to show which team is assigned what work, but it would be useful to be able to plot out the roadmap showing team assignment - eg show what things are assigned to what ...
Guest
about 9 years ago
in Features
0
Already exists
Very similar to APP-I-2199 I want to be able to group custom fields into distinct groups. For example I have a section that is all dates controlled by our development team. I would like to take those fields and group them together into one section...
Guest
about 9 years ago
in Features
1
Already exists
I have seen similar requests among the ideas, but not quite this "ask." We need a single custom field to be shared among several product lines so that we can use it in reporting. Right now, we have the same custom field in each product line (creat...
Guest
about 9 years ago
in Features
1
Already exists
Add field for "Original" or "Primary" Assignee for features
When we create a feature that becomes work for a developer in JIRA, we assign the ticket to a primary/original developer. When the work is done the ticket is assigned for code review and then again for QA. What gets lost is who the primary/origina...
Cy Caine
about 9 years ago
in Features
0
Already exists
The colored features tags that appear at the features board are linked to the default "Tags" property. I would like to configure fixed values for "Tags" property.
Guest
about 9 years ago
in Features
0
Already exists
Show also the related features name instead of the related feature link.
If I add a Bug Fix related with an existing feature I would like to link the bug fix to the feature and see both names at features list.
Guest
about 9 years ago
in Features
0
Already exists
When using requirements for estimations as an input to roadmap planning, it would be helpful to be able to add a standard set of requirements to the feature, for example where each requirement might identify a different resource type for estimatio...
Guest
about 9 years ago
in Features
3
Already exists
In order for developers to be able develop exactly what is required, validation or acceptance tests must be added to user stories. Each User Story should be able to have numerous Acceptance/Validation tests. This will assist in assigning effort an...
Guest
about 9 years ago
in Features
0
Already exists
I've recently started to use requirements within features more - and see them as a good way to clear a lot of unnecessary detail from feature overviews / reports. However to change a large number of features into requirements is a slow one-by-one ...
Guest
over 9 years ago
in Features
4
Already exists