-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. We have reviewed this issue over the last few days; unfortunately we don't have any plans to work on this in the foreseeable future.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original Request
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.
- is duplicated by
-
JRASERVER-9810 Subtasks are not displayed in the Release Notes
- Gathering Impact
-
JRASERVER-7745 Allow to configure the issue types for change log and release notes generation
- Closed
-
JRASERVER-8522 Option to remove / hide sub-tasks from Release Notes
- Closed
- is related to
-
JRASERVER-8290 subtask don't appear in issue navigator
- Closed
-
JRASERVER-9561 Allow source control (e.g. CVS) information to be included in release notes
- Closed
-
JRASERVER-40990 Using filters to create changelogs.
- Closed
- relates to
-
JRASERVER-10404 Make 'views' of content (single issue and search request) pluggable, and rewrite default implementations in velocity
- Closed
-
JRACLOUD-88131 Option to remove sub-tasks from roadmap / changelog / Release Notes
- Gathering Interest