-
Suggestion
-
Resolution: Won't Fix
-
None
-
4
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Thanks everyone for your feedback. After consideration, we are closing this issue because we do not expect to address it in the foreseeable future. As is clear from the examples below, the ideal propagated action depends on the type of issue link and varies depending on your use case. Considering issue links can be arbitrarily defined, this would require adding logic in JIRA to handle certain types of links differently from others. Alternatively, we would need to add settings to configure propagated actions based on the issue links.
Our belief is that the value doees not justify the expected increase in UI complexity or maintenance burden.
As always, please don't hesitate to contact me if you have any questions.
Thanks
Dave Meyer
Product Manager, JIRA Platform
When an issue is linked as solved by or set as duplicate do a cascading update when resolving the issue that solves the duplicate.
- duplicates
-
JRASERVER-2582 Ability to do issue threading for the purpose of tracking individual requirements or tests that are spawned from an original issue
- Closed
-
JRASERVER-17109 Linked Issues should perform actions when one issue is resolved
- Closed
- is duplicated by
-
JRASERVER-1502 Cascade update statuses to dependent issues
- Closed
-
JRASERVER-2678 When resolving, automatically resolve duplicate issues
- Closed
-
JRASERVER-10959 Bulk change status of all linked issues
- Closed
-
JRASERVER-16738 Need ability to create and link issues as part of a workflow
- Closed
- is incorporated by
-
JRASERVER-11934 Provide pre and post link hooks
- Closed
- is related to
-
JRASERVER-2678 When resolving, automatically resolve duplicate issues
- Closed
-
JRASERVER-4302 Transferring settings through issue linking
- Closed
-
JRASERVER-11125 JIRA 4.0 Enterprise Requirements
- Closed
- relates to
-
JRACLOUD-2735 Propogate actions/transitions to linked issues
- Closed
-
JRASERVER-2938 Propagate watches through linked issues
- Closed
-
JRASERVER-3009 Calculate issue estimates using subtask estimates
- Closed
-
JRASERVER-3569 Improved use of nested (linked) issues
- Closed