-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
To further enhance the ability to organaise issues the following could be done:
1. Items (issues) could be bulk-added to containers.
2. Time estimates for items within a container should automatically be aggregated. For example: If the container holds two tasks with 1 day and 2 days remaining, the container's remaining days should be 3.
3. Reports shouldn't double-count the time estimates of container tasks and the tasks that they contain.
4. You should have the option to manipulate contained items along with their containers. For example, if you change the Fix Version for a container task, all of the contained tasks should optionally be moved to that new Fix Version as well.
5. It would be nice if containers could hold other containers, but first-round usefulness wouldn't depend upon this.
6. It would be nice if there were default searches that would automatically display these roadmap views for a given project, but first-round usefulness wouldn't depend upon this.
Please vote for the issue and andd any comments that you may have.
- is related to
-
- Closed
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-6495] Organise issues into containers or queues
There is another similar customer request and related discussion for this at http://forums.atlassian.com/message.jspa?messageID=257320031&tstart=0
~Matt
Hi,
This is a bulk update to specific issues in the JIRA (JRA) project
As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.
Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com
If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.
Best regards
Josh Devenny and Roy Krishna
JIRA Product Management