A bit disappointing, feels like this is way to further draw out the resolution time and kick the can down the road, you might be better off just declining items that will not be actioned, so we know where we stand. Additionally, will the new items be linked to the ones that have been closed so we can continue to track them?

Will the people who were originally following this item (to see progress of the child items) be added to each of the new ones as watchers, or do we need to find each one ourselves to do that?

I believe these are all the open issues that were moved out:

1. JRACLOUD-72186 Ability to configure quick-add buttons in new issue view
2. JRACLOUD-73196 Ability to expand the comment section at once in the new issue view
3. JRACLOUD-71306 Field Rank is not being displayed on the new issue view
4. JRACLOUD-76182 Preview for attachment only allows navigating through 6 attachments at the time
5. JRACLOUD-80141 Using middle click to open a linked issue in the new issue view duplicates opened link in Firefox
6. JRACLOUD-76004 Display author in the attachment's list in the new view
7. JRACLOUD-75577 Statuses to be shown as buttons instead of a unique drop-down button list
8. JRACLOUD-78919 New view on Transition Issue screen
9. JRACLOUD-76192 Ability to pin fields through screen scheme
10. JRACLOUD-77086 Unable to make "Assignee" non-editable in NewIssueView
11. JRACLOUD-77516 Have third-party apps' frames persist on the new issue view
12. JRACLOUD-71827 Dot "." menu is missing "Epic Link" and other actions
13. JRACLOUD-73770 Add markdown support for task lists
14. JRACLOUD-76124 As a Jira admin, I want to be able to edit the number of characters shown in a custom multi-select field
15. JRACLOUD-75992 Date time picker shows 12 AM/PM as 0 AM/PM
16. JRACLOUD-76142 Multi line text field not highlighting URL as hyperlink
17. JRACLOUD-74599 Remote links or web links should display the link summary in new issue view
18. JRACLOUD-70206 Configuring the info to show when viewing sub-tasks or linked issues in a table does not reflect in the new issue view
19. JRACLOUD-72742 Ability to Assign and Comment at the same time on the new issue view
20. JRACLOUD-74967 Number of Comments Custom Fields are not displayed on the New Issue View
21. JRACLOUD-78149 Resolution not displayed unless the page is reloaded
22. JRACLOUD-78854 Unable to move fields to hidden for the custom tabs in issue layout
23. JRACLOUD-72797 Ability to change created/updated fields location
24. JRACLOUD-77816 Ability to display the Resolution as Unresolved
25. JRACLOUD-76244 Standardize fields under the Description fields area in Issue layout
26. JRACLOUD-76714 Availability to Drag and Drop Attachments from issues to Desktop/Folders
27. JRACLOUD-75885 Disable back button in a screen tab in new issue view until the required field is poulated
28. JRACLOUD-71781 Unable to view full name of attachment in new issue view
29. JRACLOUD-74420 Date Picker on New Issue View should have "Today" option
30. JRACLOUD-76424 Tooltips for workflow transitions on New Issue View
31. JRACLOUD-72556 Ability to collapse add-on fields or keep the content expanded in the new issue view
32. JRACLOUD-74166 When the field is set on "View issue" screen and not "Edit issue" the field disappears after loading the page (New issue view)
33. JRACLOUD-76057 New View's custom User Picker (multiple users) should look like Old Issue View
34. JRACLOUD-69548 Configuring the default order of actions to desc. in advanced settings does not reflect in the new issue view
35. JRACLOUD-76581 Add feature to restrict the work description message when using Log Work as in the old issue view
36. JRACLOUD-78008 Enable real time updates even when add-ons are installed
37. JRACLOUD-76559 Add a Tooltip showing the description for "Components"
38. JRACLOUD-76515 Have the new view remember the last used issue link option
39. JRACLOUD-76047 Ability to sort attachments in Strip View (Thumbnail) in New Issue View
40. JRACLOUD-73418 Sub-tasks in the new issue view no longer wraps their summary
41. JRACLOUD-76535 Ability to resize the comment box (New Jira issue View)
42. JRACLOUD-69810 Time tracking format of logged-time does not respect Time Tracking setting in Activity > Worklog section
43. JRACLOUD-76316 Display transition name when only "All" is available
44. JRACLOUD-79368 Scrollbar for Long Comments
45. JRACLOUD-74778 Ability to hide or collapse the issue links panel in the new issue view
46. JRACLOUD-70073 Unable to edit issue with edit issue screen from new issue view
47. JRACLOUD-73048 Make file markup available in the new issue view
48. JRACLOUD-76703 Sort Components dropdown list alphabetically
49. JRACLOUD-73516 Display the Issue Type name on New Issue View
50. JRACLOUD-77108 Availability to collapse Description field
51. JRACLOUD-74856 Advanced Search in issue linking is not available in new issue view
52. JRACLOUD-76203 Ability to disable/hide New Issue View top buttons (create subtask, attachment, link issues)
53. JRACLOUD-74680 Ability to control the number of comments to collapse
54. JRACLOUD-73163 Code block/snippet in the new issue view
55. JRACLOUD-76103 Markup support for New Jira Issues
56. JRACLOUD-77188 Add option to toggle line numbers off in code block macro settings
57. JRACLOUD-72060 There is no way to add sub-tasks to epics using the new issue view.
58. JRACLOUD-76407 Editing a Cascading Select field with only a first-level existing value makes it difficult to edit or even know about a possible second value
59. JRACLOUD-76349 Story Points custom field can be edited/viewed even though the field is removed from the Edit/View screens
60. JRACLOUD-73176 Inconsistency in Performance between New and Old Issue View
61. JRACLOUD-72506 Creating a subtask / issue in Epic should open in a pop-up
62. JRACLOUD-70150 Sub-tasks no longer have their time tracked on the parent issue for the new Full View Issue experience
63. JRACLOUD-70957 Add Transitions Tab to the New Issue View
64. JRACLOUD-72024 Ability to reorder the Activity tabs (e.g. comments, history)
65. JRACLOUD-76253 Add option to collapse the right panel of the new issue view

Hi @Ahmud,

Where we can see this part from your last comment: "We will be closing the existing parent issue and converting each open sub-task into its own individual task."

I ask since I think it will not help much for creating duplicate tickets.

Kind regards,
Mher

Hello Everyone,
 
We are making an important change to our feature request process for the Issue View.
To enhance our development workflow and improve overall efficiency, we have decided to revise the way we handle feature requests. We will be closing the existing parent issue and converting each open sub-task into its own individual task. This change will allow us to better track and manage the valuable input and feedback we receive from our dedicated user community. This change brings us in line with our standard process for how we manage feature requests for all other Atlassian experiences.

We highly value your feedback and encourage you to continue sharing your ideas and suggestions through these Jira tickets. Your input plays a crucial role in shaping the future of our product, and we remain committed to improving the issue view.

If you have any questions or concerns regarding this transition, please feel free to reach out to our support team via[ creating a support request|https://confluence.atlassian.com/support/create-a-support-request-790796816.html].

Thank you,

Ahmud |

hello Atlassian team,

Are you planing to fix  "FTP/SFTP address is recognized as an email address - when you click on it, a new email message is composed."

Atlassian more and more becomes famous for "screw the customers and twist the facts to suit our needs"

@Steven Rhodes, and par for the course Atlassian is calling this regression bug a suggestion/feature request. This used to work in the "old view" but does not work in the "new view" – but they consider the "new view" an entirely different product, so these are not regression defects... these are features to add to the new view when they get the time.

What is the point of having a History tab with the old descriptions if you can't copy paste from the history into the description field? Its broken. https://jira.atlassian.com/browse/JSWCLOUD-24144

you cannot add the issue type in any of the layout sections, and yet it is not visible.

This needs to be fixed asap for adoption as many workflows are dependent on the issue type for conditions and transitions, hiding it in the breadcrumbs will be a major issue