-
Suggestion
-
Resolution: Fixed
-
None
-
1
-
6
-
Problem Definition
At this moment, it is not possible to control the sub-task (assigne, edit, rank, etc) or child issues (inside Epics) from the parent issue using the "New Jira issue view", as it could before. The video below better demonstrates this feature currently: JRACLOUD-72328.mp4
In the old issue view, the feature had more options as the image below:
Suggested Solution
Add the More ••• on each sub-task, while viewing them from the parent issue, like before. Another possible approach would be having the ability to drag and drop to reorder issues inside Epics or Stories with Sub-Tasks.
Why this is important
This should improve the experience for users using the "New Jira issue view".
Workaround
- Users can either click on the sub-task to access it directly and then edit it accordingly or;
- Users can disable the "New Jira issue view" for now, by:
- Clicking the profile icon, on the bottom of the left sidebar, then Settings under "JIRA";
- On the "Jira Labs" section, clicking to disable the New Jira issue view.
- is related to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
[JRACLOUD-72983] As a user, I'd like to control the sub-task or child issues (assign, edit, rank, etc) from the parent view as I could before
@Anusha Rutnam, I agree the ranking to top or bottom on a parent issue, is separate from subtask management under a parent, Epic or not. Whether or not rank to top or rank to bottom, Agile board or Comment is restored for subtask management from the parent issue view, is up to Atlassian: this is less critical for Backlog management.
I would recommend restoring those lost features on an issue level first, before restoring them on parent view level.
I think the following may have changed since this issue was first created.
In company-managed projects you can change a subtask's assignee and status while viewing the parent task:
The same is true of team-managed projects when viewing the Child issues section of a parent issue.
I believe the remaining ask of this ticket, the ability to rank these child issues is covered in the separate feature request previously mentioned in comments here: JRACLOUD-75253 – "Rank to top" and "Rank to bottom" should be shown inside of an issue type e.g.: TASK in the New Jira issue view.
Can the watchers of this issue let me know if there are any actions apart from Ranking that they are still missing from this view? Thank you!
This issue doesn't just apply to subtasks, it applies to parent tasks.
The old menu contains 2 critical features "Rank to top" and "Rank to bottom", that are still not present in the new Jira issue view.
This issue should get a higher priority if Atlassian intends to disable the old view.
If you need more votes, simply read the comments placed by users under:
https://jira.atlassian.com/browse/JRACLOUD-75253 as well as https://jira.atlassian.com/browse/JRACLOUD-70555
and understand the importance of the use case, managing a backlog as a product owner.
Thank you for sharing your use cases for updating subtasks from the parent view. We are working to bring a range of improvements to the new issue view. To be as transparent as possible I wanted to let you know that we will not be prioritising this issue in the short-term. We will leave this ticket open for you to provide further context and will continue to monitor this ticket for updates and will let you know if we are able to prioritise it.
As per this comment I am closing this ticket. Please note that the rank feature request can be tracked here: JRACLOUD-75253 – "Rank to top" and "Rank to bottom" should be shown inside of an issue type
A related request, the ability to add more columns to the sub-task / child view when viewing the parent issue may be followed here:
JSWCLOUD-16211– Add facility to change what is displayed in the Child issues (formerly 'Issues in Epic') panel when viewing epicIf you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.