New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-7835
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 22
Watchers: 12
Operations

If you were logged in you would be able to see more operations.
JIRA

Option to remove sub-tasks from roadmap / changelog / Release Notes

Created: 02/Sep/05 04:03 AM   Updated: 08/Oct/07 01:59 AM
Component/s: Reports, Web interface
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference

Participants: Ahmad Masrieh, Anton Mazkovoi [Atlassian], Jeff Turner [Atlassian], Kevin James, Melissa, Miro Lehky, Nick Menere [Atlassian], pierre-yves voirol and Sergiy
Since last comment: 45 weeks, 2 days ago
Labels:


 Description  « Hide
Often an issue represents a high-level view of an issue, and subtasks are low-level implementation details. Consequently the sub-tasks are not of much interest on the project reports (changelog, roadmap, Release Notes). We should provide a checkbox to remove them.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] added a comment - 02/Sep/05 04:05 AM
If we rendered each roadmap entry with a CSS class, it will be easy to hide subtasks with Javascript or by editing the CSS.

Miro Lehky added a comment - 15/Sep/05 08:22 PM
This will be a very handy feature.

pierre-yves voirol added a comment - 03/Nov/05 11:40 AM

Very good idea !!

IMHO you should provide a solution that let the user choose it's "default state" for the checkbox.

Idea :

1) implement a checkbox in User's preferences (like the "Email me when i make changes") -> Substaks hidden in Roadmap / Changelog
2) implement a checkbox in Roadmap / Changelog (initialized with value found in User's preferences)


Jeff Turner [Atlassian] added a comment - 03/Nov/05 06:04 PM
CSS isn't a nice solution because the issue counts won't change, so it's a bit more work than anticipated.

Ahmad Masrieh added a comment - 15/Nov/05 06:51 AM
To be consistent, please extended this improvement to exclude / hide / remove also include Release Notes from reporting.
  • hide sub-tasks from Road Map
  • hide sub-tasks from Changel Log
  • hide sub-tasks from Release Notes

And for the project lead or management point of view (if you need to hide the details), JRA-5869 will do the job.


Nick Menere [Atlassian] added a comment - 15/Nov/05 05:18 PM
Ahmad, nice suggestion.
I have changed the summary to include Release Notes.

(I will resolve the other issue you raised as a duplicate).


Ahmad Masrieh added a comment - 16/Nov/05 02:16 AM
Nick, thanks for the feedback and clean up. I will add my details about the release notes her.

Suggestion about how to implement the release notes part:

Sample 1 - extended the existing release notes screen

  • Please Select Version:
    • 1.0
    • 2.0
  • Please Select Style:
    • HTML
    • HTML without Sub-Tasks
    • Text
    • Text without Sub-Tasks

Sample 2 - add an additional option to existing release notes screen

  • Please Select the Issue Types to include:
    • All Issues
    • Only parent Issues without sub-task
    • Only sub-task withouth parent Issues

Ahmad Masrieh added a comment - 16/Nov/05 06:32 AM
Please review this post

and consider this issue as a part of a greater whole.

Ahmad


Anton Mazkovoi [Atlassian] added a comment - 02/Jan/06 06:51 PM
We are planning to revisit sub-tasks in 3.6. We will have a look into this issue then.

Kevin James added a comment - 18/Jan/06 03:28 PM
I would suggest extending to enable/disable reporting of any issue type in the Roadmap, Changelog, and Release Notes. We have created a new issue type called Requirements as a means for capturing Business Requirements as defined by business analysts. We use Confluence to capture a business requirements document, but the actual requirements are entered directly into JIRA and a portlet is displayed in the Confluence document. From these Requirements, developers generate Features Requests, Improvements, and Refactor issues that are linked directly to the Requirements. They may even link existing Bugs to a Requirement.

However, when we generate, say Release Notes, we'd really just like to show Feature Requests, Improvements and Bug. We'd like to hide Requirements, Refactor, Sub-tasks and TestCases (another type of Sub-task).


Melissa added a comment - 02/Jun/06 12:34 PM
This would also be hugely beneficial for my team, especially if extended as Kevin suggests.

Ahmad Masrieh added a comment - 02/Jun/06 01:31 PM
Unfortunately I appended by mistake a '_' character to the URL – this leads to a dead link

And because of JRA-1100, I'm not able to correct all posts with the wrong URL

Please review using the corrected link: http://forums.atlassian.com/thread.jspa?threadID=9146

Ahmad


Ahmad Masrieh added a comment - 19/Oct/06 05:09 AM
removed from JIRA 3.7 - really bad news

What about using a pre-defined filter as an input list for the Release-Notes output? Would it help to get this feature for 3.7.1 ......?


Sergiy added a comment - 08/Oct/07 01:59 AM
It would very useful improvement. We look forward to it in the nearest update.
I have given my vote for this issue.