Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-78919

Upgrade the issue transition screens to the new experience

XMLWordPrintable

    • 659
    • 121

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      24 June 2024

      Hey everyone,

      It’s here! I’m super thrilled to share that starting this week, we’re rolling out the new issue transition experience for all Jira sites! Read more in our community post here!

      As always, thank you for your patience.

      Best,
      Arbaaz Gowher
      Product Manager, Jira

      25 April 2024

      Hey everyone,

      I’m excited to announce that we’ve now opened up signups for the early access program to the new issue transition experience! Learn more about the improvements we’re making and how to sign up for the early access program.

      Thanks as always for your patience.

      Best,
      Arbaaz Gowher
      Product Manager, Jira

      14 August 2023

      Hey everyone,

      We've picked this up and are modernising the Issue Transition experience akin to how we modernised the Issue Create experience a while back. Please watch this ticket for updates!

      Additionally, if you'd like to share anything about the current experience or what you expect in the new experience, please feel free to book a time/date here.

      Thanks as always for your patience.

      Best,
      Arbaaz Gowher
      Product Manager, Jira Cloud

      The issue transition screens continue to behave like the old issue create and view experiences. It would be great to upgrade them to the new experience.

            [JRACLOUD-78919] Upgrade the issue transition screens to the new experience

            Abhishek Yadav made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 981325 ]
            Matthew Hunter made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 971729 ]

            Bernhard G. added a comment -

            Atlassian at its best!
            Lots of people complaining missing basic functionality, but it's still a feature request, not a bug.
            So all of them waiting for ages to get this fixed.
            Also promises are done that they will be provide a 100% solution.
            And what happens? The same sh** as everytime! Work is maximum 50% done, feature request is closed, Atlassian is proud to announce a new transition screen nobody needs as the main functionality is missing and for all the people really need, a new feature request is opened where the idiots of customers can start voting and waiting again.
            Nobody is happy except Atlassian product management, because in there statistics it looks good because the old feature request is closed...
            Moreover they don't care or react in any way to customers feedback, or why did you not answer to my comment https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3543013&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3543013?
            7645729f7e9f Maybe you want to answer at least to that one? I would be curious why did you break your promises?

            Bernhard G. added a comment - Atlassian at its best! Lots of people complaining missing basic functionality, but it's still a feature request, not a bug. So all of them waiting for ages to get this fixed. Also promises are done that they will be provide a 100% solution. And what happens? The same sh** as everytime! Work is maximum 50% done, feature request is closed, Atlassian is proud to announce a new transition screen nobody needs as the main functionality is missing and for all the people really need, a new feature request is opened where the idiots of customers can start voting and waiting again. Nobody is happy except Atlassian product management, because in there statistics it looks good because the old feature request is closed... Moreover they don't care or react in any way to customers feedback, or why did you not answer to my comment https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3543013&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3543013 ? 7645729f7e9f Maybe you want to answer at least to that one? I would be curious why did you break your promises?

            Dave Meredith added a comment -

            I'm not sure why this piece of work has been closed as 'Fixed'? The new issue experience does not have feature parity with the old experience as Assets is excluded.

            Why has this been separated out into a different ticket? The expectation from this ticket was to have all functionality from the old experience made available in the new experience?

            Dave Meredith added a comment - I'm not sure why this piece of work has been closed as 'Fixed'? The new issue experience does not have feature parity with the old experience as Assets is excluded. Why has this been separated out into a different ticket? The expectation from this ticket was to have all functionality from the old experience made available in the new experience?
            Daniel Ocando Espinoza made changes -
            Link New: This issue causes JRACLOUD-85466 [ JRACLOUD-85466 ]

            Daniel Ocando Espinoza added a comment - - edited

            All updates about the integration of the Assets field will be posted here https://jira.atlassian.com/browse/JRACLOUD-85466 

            Daniel Ocando Espinoza added a comment - - edited All updates about the integration of the Assets field will be posted here https://jira.atlassian.com/browse/JRACLOUD-85466  

            Birger Robrecht [avono AG] added a comment -

            Is there any issue that tracks the integration von Asset Custom fields into the new transistion experience? Assets are used by a lot of my JSM customers, so I'd like to track the progress of the development.

            Birger Robrecht [avono AG] added a comment - Is there any issue that tracks the integration von Asset Custom fields into the new transistion experience? Assets are used by a lot of my JSM customers, so I'd like to track the progress of the development.

            Aleksander Valler added a comment -

            Hello, like fc00a64f2a44 , we are using Assets fields in transition screens, and it is necessary for us to have the functionality further. As long as the Assets fields cannot be used in "new experience transition screen", the old experience must be available. From my point of view, Atlassian cannot close the ticket without support for all field types inclusive Assets fields.
            It is clear, that Assets fields are not fairly supported by Atlassian. Assets fields are not supported by migration Server -> Cloud or Cloud -> Cloud. But Assets fields are the important functionality piece, which decisively influences the purchase of Atlassian product. We want to see better support for it!

            Aleksander Valler added a comment - Hello, like fc00a64f2a44 , we are using Assets fields in transition screens, and it is necessary for us to have the functionality further. As long as the Assets fields cannot be used in "new experience transition screen", the old experience must be available. From my point of view, Atlassian cannot close the ticket without support for all field types inclusive Assets fields. It is clear, that Assets fields are not fairly supported by Atlassian. Assets fields are not supported by migration Server -> Cloud or Cloud -> Cloud. But Assets fields are the important functionality piece, which decisively influences the purchase of Atlassian product. We want to see better support for it!

            Rick Westbrock added a comment -

            We’re slowly moving users from the old experience to the new experience to ensure one experience for all of you.

            We use Assets fields in many transition screens, how are you preventing our users from being transitioned to the new experience so that our processes are not broken?

            Rick Westbrock added a comment - We’re slowly moving users from the old experience to the new experience to ensure one experience for all of you. We use Assets fields in many transition screens, how are you preventing our users from being transitioned to the new experience so that our processes are not broken?

            Bernhard G. added a comment - - edited

            91a6d4b3a588 I was already afraid of exactly this situation in June/July - please see the following 2 comments:

            7645729f7e9f What's about your promises in July? Now, already a lot more than 8 weeks later, everybody gets the new transition screen without closing all gaps? What did you do in the mean time?

            Bernhard G. added a comment - - edited 91a6d4b3a588 I was already afraid of exactly this situation in June/July - please see the following 2 comments: https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3470059&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3470059 https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3470650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3470650 7645729f7e9f What's about your promises in July? Now, already a lot more than 8 weeks later, everybody gets the new transition screen without closing all gaps? What did you do in the mean time?

              7645729f7e9f Arbaaz Gowher (Inactive)
              itrojahn@atlassian.com Ilenice
              Votes:
              345 Vote for this issue
              Watchers:
              217 Start watching this issue

                Created:
                Updated:
                Resolved: