Rolling out the new JIRA experience to your Cloud add-on customers

Hey David,

…my add-on won’t have any way to know which UI experience is current for the user; is that right?

Correct.

I’m concerned about any aspect of the new UI experience that might make my add-on present a bad user experience…Can you conceive of any situations like that, and if so, how do you suggest that add-ons handle it?

Aside from the locations we have previously stated as being removed in the new experience, your add-on’s user experience shouldn’t be significantly impacted.
If you do feel your add-on’s experience has been reduced significantly by these changes, I recommend optimising for the new interface. I wouldn’t wait until the old UI experience has been completely phased out.

Should we be trying to make our add-ons work during the transition?

There should be no work required to make your add-ons to be functional. If you find an issue, please raise a bug as mentioned in the post.

What approach do you recommend that we take?

I recommend optimising for the new JIRA experience. It may make sense to optimise in smaller increments while more JIRA users are adopting the new UI, but the existing interface will only last another few months.

We will continue to communicate milestones during this rollout to help provide clarity.

1 Like