-
Suggestion
-
Resolution: Fixed
Hi all,
We're excited to announce that the ability to split issue is available in JIRA Software 7.5 starting from today!
We really appreciate your patience with this feature request, and apologize for our silence on the matter. We also appreciate the insights in this thread - it helped a ton in the design and prioritization of split issue.
As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps (read more here), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server.
JIRA Software 7.5 is now available to download so you can start planning your upgrade straight away!
Learn more in our release notes.
Cheers,
Jakub Lazinski
Product Manager, JIRA Server
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Sometimes some issues grow to span several problems. This can happen very often at early stage of Jira adoption.
It would be very nice to have ability to easily split issue in two ones, without a mailstorm.
Desirable options for extracted issue:
- copy some fields/metadata, set new values to others
- move selected comments
- move selected attachments
All this should produce only one notification.
- is related to
-
JSWSERVER-16204 Remaining Estimate not updated with Split issue feature
-
- Gathering Impact
-
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
