Improvements on Updating issue type
Improving the issue type update experience for customers to feel more confident when using Jira.
Introduction
Customers utilising Jira, an Atlassian product, have consistently had questions around how to update issue types and have searched for clarity around that action. Which often left customers deleting an issue and re-creating the issue again with the updated issue type. In this project we wanted to help customers who are updating their issue type.
The challenge
The goal of this project was to improve the user’s experience when changing the issue type of an issue, particularly when issue type changes between types are not compatible. Incompatible issue types redirect the user to a dated experience, and the user has no indication that this redirect will occur until they find themselves on a different page.
In an ideal world and uplift of that dated experience would be the solution, however taking into consideration our timeline and our team’s expertise a total uplift of that area would not be possible at this moment. There are other technical challenges that influenced the amount of change we are able to implement, as legacy areas of Jira and the “fresher” areas of Jira meet within the change issue type flow. But to still provide value to our customers a different solution could still be provided.
The outcome
In order to solve this problem I designed a solution that aligned with our design system and could also be completed within a quick time period for our engineering team. By understanding the technical complexity I was able to design a few iterations of this improvement one where we are in an ideal world and would require a larger timeline and a solution that could be implemented within a sprint (2 weeks).