so that I can save time in grooming and I can see all information for what I am splitting.
Example Scenarios:
- I created an epic that is too large. I want to split it into 2 and re-define requirements across two epics.
- In grooming, one story is estimated too large. I want to split it into two stories
Current Solution:
Cloning - However, I lose track when using two tabs. I would do it away from the team and they have to wait on a future grooming to re-estimate.
- is related to
-
JSWSERVER-4542 As a user I would like to quickly duplicate an issue to split a story into two
- Closed
- mentioned in
-
Page Failed to load
[JSWSERVER-9929] As a Product Owner I want to split an epic easily
Workflow | Original: JAC Suggestion Workflow [ 3068656 ] | New: JAC Suggestion Workflow 3 [ 3663638 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2625319 ] | New: JAC Suggestion Workflow [ 3068656 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327407 ] | New: Confluence Workflow - Public Facing v4 [ 2625319 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2044244 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327407 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032436 ] | New: JIRA PM Feature Request Workflow v2 [ 2044244 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 736137 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032436 ] |
Labels | Original: epic epics triaged | New: epic epics sw-c sw-split triaged |
Remote Link | Original: This issue links to "Page (Extranet)" [ 92071 ] | New: This issue links to "Page (Extranet)" [ 92071 ] |
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers) within the last year.
We hope you will appreciate our candid and transparent communication. You can read more about our approach to highly voted server suggestions here.
To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.
Regards,
Jira Server and Data Center Product Management