Sign up for the EAP to the new issue transition experience

[#1]

Update on June 24, 2024

We're super thrilled to share that we're starting the rollout of the new issue transition experience to GA this week! Please read this community post for more information.

Update on June 10, 2024

Good news—the new experience will support the following fields starting the week of June 17!

System and Software fields:
Environment, DueDate, Reporter, Security, Summary, Sprint, Epic Label, Story points, Cascading select, Time tracking, Message Custom Field(for Edit), Flagged Field

Standard custom fields and JPO fields:
Custom field number, Single Version custom field, Multi-version custom field, Multi-user picker, Custom people field, Single Group picker, Multi group picker, Target start locked field, Target End locked field, JWM Category Custom Field, Project Picker(Single Project), Custom Date Time Picker Field

Standard JSM fields:
Impact, Actual end, Actual start, Affected Hardware, Approver Groups, Approvers, Backout Plan, Change reason, Change risk, Change type

Additionally, some customers may be affected by changes affecting workflow validators and post functions on the new issue transition experience. You can learn more here.

---

Original post from April 26, 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! This applies to software, business and service projects.

What’s the issue transition experience, you ask? So you know how you can click the status dropdown on an issue to go from, say, TO DO → IN PROGRESS → DONE? Jira admins can configure screens to solicit additional or modify existing information (read field values) when an issue goes through a workflow transition from STATUS A → STATUS B. For example, before transitioning an issue to an OBSOLETE status, a knowledge worker may be mandated to input additional information required by the workflow transition as to why the issue is now obsolete.

So, what’s new?

Similar to how we modernised the issue view and issue create experiences a while back, we’re modernising the issue transition experience. You’ll notice the following improvements:

1. Adding comments using the new ADF editor, and yes, that includes Atlassian Intelligence

2. Comments on service projects will default to internal visibility

3. Reference existing attachments when adding new comments

4. Search for specific values inside fields

5. Modern look and feel and so much more!

We’re starting with support for the following fields:

• System and Software fields:
  Attachment, Assignee, Components, Description, FixVersions, Versions, IssueLinks, IssueType, Labels, Priority, Resolution, Single user picker, Custom Atlassian Team Field, Worklog, Comment, Start date, Linked Issues, Flagged, Impact

• Standard custom fields and JPO fields:
  Custom textarea field (Paragraph), Custom field labels, Date picker, Date time picker, Select custom field, Multiselect custom field, Radio custom field, Checkboxes custom field, Custom text field, Custom URL field

Coming soon

1. Canned responses for service projects

2. Support for team-managed software and business projects

3. Support for changing the background colours of cells on a table in Jira

4. Support for the following fields:

   • System and Software fields:
     Project, Environment, DueDate, Reporter, Security, Summary, Sprint, Epic Label, Story points, Cascading select, Time tracking, Message Read only Field

   • Standard custom fields and JPO fields:
     Custom field number, Single Version custom field, Multi-version custom field, Multi-user picker, Custom people field, Single Group picker, Multi group picker, Target start locked field, Target End locked field, JWM Category Custom Field, Forge Custom Fields, Connect App Custom Fields

   • Standard JSM fields:
     Request language field, asset field, customer organisations, Request Participants, Service Entity Field

Please note that if you have any of the above fields configured on your screen and they’re required, you’ll not be able to transition the issue using the new experience. In this case, you’ll need to either switch to the old experience or make the fields optional.

What’s the eligibility criteria?

• A paid license (Standard, Premium, or Enterprise).

• Roughly 10 issues transitioned per user (of the enrolled tenant URL) weekly.

When does the early access program start, and how can I sign up?

If you meet the above eligibility criteria, sign up for the early access program.

We’ll enable the new experience on the tenant URL you share in the week of May 20, 2024. Don’t worry. We’ll send you a confirmation email before we switch it on if you have a change of heart!

How do I share feedback?

Your feedback will be of utmost significance in enabling us to improve the new issue transition experience for you and everyone else. There are two ways in which you can share feedback:

• Submitting general feedback or a bug report on the EAP portal allows you to be in direct contact with the product team.

• You can also submit feedback by clicking the feedback icon on the top-right corner of the screen. However, note that we aren’t able to respond to any feedback shared from here.

What if something goes wrong, and I want to switch to the old experience?

Easy. At any time, you’ll have the following options:

• At a user level, if users don’t want to use the new experience for any reason, they can switch to the old experience by cliking the the profile picture/initials > Personal settings > Jira labs > toggling the New issue transition experience button off. The switch is instant.

• At the tenant level, Atlassian can switch off the new experience for all users in a tenant. You can request via the EAP portal. The maximum turnaround time for Atlassian to respond to your request to switch the experience off for all users will be 24 hours.

What’s the level of engagement expected if accepted into the early access program?

Once the new experience is enabled for your tenant URL, we request you to:

• Track issue transition performance and usage

• Elicit feedback from users to understand the usability

• Offer suggestions on how the experience can be further improved

We can’t wait to get the new and improved experience in your hands! Feel free to ask any questions you may have! I’m here and eager to listen to you.

Sign up today!

Thanks as always,
Arbaaz Gowher
Product Manager, Jira

[Dan W]

Just curious, why did you decide to make "Comments on service projects will default to internal visibility"  In my experience at least most comments I am leaving on a service ticket are meant for the reporter and I select internal when needed.  Seems backwards to me

[Greg D]

@Dan W I saw your comment here after JSDCLOUD-9463, but just to echo what I wrote there, internal being the default is much less risky in case an agent is writing internal details, sensitive info, mentioning internal people, or confusing directions that will not make sense externally.

But would definitely love to have more control with the defaults and who can even write external comments.  Hopefully this restricting of who can write external comments on JSDCLOUD-9677 is folded into the work on JSDCLOUD-829 too.

There are definitely use-cases where certain roles or projects might need only external (we have more of the reverse where we need to only show internal), but would love more control!

[Rick Westbrock]

With so many fields listed as incompatible when required is there a roadmap to allow that in the future? Specifically we have some Assets fields on transition screens which are required so we can't use the new experience until that is supported.

[Richard Shepley]

Are we now going to be able to hide the "comment" section from transition screens that don't require comments? 

[JRACLOUD-12244] Allow control of whether comment field will be shown on Edit and Transition screens - Create and track feature requests for Atlassian products.

[Joachim Bollen]

When will Asset fields be supported? Is there an ETA for this?

[Jeremy Lowrey]

@Greg D  It would be helpful to understand the current state of the Early Access Program (EAP) for this product. As a potential early adopter, I'm interested in accessing the new features as soon as possible. However, I need to carefully weigh the potential risks that any bugs or issues could pose to the daily productivity and reliability of our team's work environment.

Specifically, I have a few key questions:

1. What is the current known status of bugs and issues that have been reported so far in the EAP? Can you provide any insights into the severity and potential impact of the known bugs at this stage?

2. Is there a formal Beta or pre-release testing phase planned for this product before the full production release? If so, would it be advisable for us to hold off on adopting the EAP features and instead wait for the more stabilized Beta version?

I'm eager to take advantage of the new functionality as soon as possible, but I also need to carefully consider the potential downsides and disruptions that bugs could introduce. Any information you can provide on the current state of the EAP and the planned release timeline would be greatly appreciated. 

[Arbaaz Gowher]

Just curious, why did you decide to make "Comments on service projects will default to internal visibility"  In my experience at least most comments I am leaving on a service ticket are meant for the reporter and I select internal when needed.  Seems backwards to me

@Dan W, as Greg mentioned, defaulting to internal comments eliminates the risk of accidentally exposing a comment to the customer. This is also consistent with the commenting experience on the issue view today.

With so many fields listed as incompatible when required is there a roadmap to allow that in the future? Specifically we have some Assets fields on transition screens which are required so we can't use the new experience until that is supported.

@Rick Westbrock good news—the new experience will support the following fields starting the week of June 17!

System and Software fields:
Environment, DueDate, Reporter, Security, Summary, Sprint, Epic Label, Story points, Cascading select, Time tracking, Message Custom Field(for Edit), Flagged Field

Standard custom fields and JPO fields:
Custom field number, Single Version custom field, Multi-version custom field, Multi-user picker, Custom people field, Single Group picker, Multi group picker, Target start locked field, Target End locked field, JWM Category Custom Field, Project Picker(Single Project), Custom Date Time Picker Field

Standard JSM fields:
Impact, Actual end, Actual start, Affected Hardware, Approver Groups, Approvers, Backout Plan, Change reason, Change risk, Change type

Are we now going to be able to hide the "comment" section from transition screens that don't require comments? 

[JRACLOUD-12244] Allow control of whether comment field will be shown on Edit and Transition screens - Create and track feature requests for Atlassian products.

@Richard Shepley, in all transparency, this isn’t on our roadmap in the short/medium term. As is with every improvement, we’ll evaluate adding this to our roadmap depending on our priorities.

When will Asset fields be supported? Is there an ETA for this?

@Joachim Bollen, unfortunately, I can’t share timelines at the moment, but support will be added!

Specifically, I have a few key questions:

1. What is the current known status of bugs and issues that have been reported so far in the EAP? Can you provide any insights into the severity and potential impact of the known bugs at this stage?

2. Is there a formal Beta or pre-release testing phase planned for this product before the full production release? If so, would it be advisable for us to hold off on adopting the EAP features and instead wait for the more stabilized Beta version?

I'm eager to take advantage of the new functionality as soon as possible, but I also need to carefully consider the potential downsides and disruptions that bugs could introduce. Any information you can provide on the current state of the EAP and the planned release timeline would be greatly appreciated. 

@Jeremy Lowrey, as a PM working on this area, I love the eagerness :) Again in all transparency, the feedback received over the last few weeks has been great. Customers love the new editor, the ability to use AI, and the consistency in UX across other Jira (create/view) experiences too. The only area the new experience (temporarily) lacks is the number of fields supported. But again, the good news is that support for 34 more fields is coming next week!

The EAP is tested well enough to be stable, but there’s always a slight possibility things may go unexpectedly due to an edge case that’s yet to be covered. Hence, we request your participation to help us identify those areas so we can improve the experience for you and everyone else. The “formal Beta or pre-release testing phase” is currently happening!

Does this answer your question?

[Rick Westbrock]

Glad to hear about more fields being supported @Arbaaz Gowher , are custom Assets fields on the roadmap yet?

[Arbaaz Gowher]

@Rick Westbrock, unfortunately, I'm unable to share the exact timeline for when the Asset field will be supported on the new transition experience yet. I can rest assure you it's on our roadmap!