In my last blog, I shared my experience with Jira next-gen, trying to be as objective about the experience as possible. If you are working in Jira cloud, you are most likely aware that there are constant changes in Classic Jira and Confluence. It is no different in Jira next-gen. From the point of coming up with the idea, outlining, and confirming my notes as I wrote the blog, next-gen had changed noticeably.

Here are my wish list features for Jira next-gen functions:

  1. Offer more guidance for selecting the next-gen project type. 
    It would be more helpful to provide a complete comparison to learn the difference between next-gen and classic projects.  Currently, when setting up a new project, a short catchphrase (‘Looking for easy setup and reimagined features?’) attempts to guide the user on which version of a project to select – next-gen or classic. When reviewing the two templates available for next-gen projects, another short paragraph for each tries to sum things up – this serves to create more questions.
  2. Simplify connecting epics.
    It would be helpful to have this as a field on creation and would save a step or two.  There is not an “epic link” field available for use during entry; it is not available to configure either. Today’s entry of epics and the supporting tasks occur separately. Once the lists are entered, a user has several clicks to find the parent link from the context menu, select the parent from a drop-down, and confirm the item.
  3. Provide additional views of issues.
    For new users, it would be helpful to have a link to the issue navigator provided which pre-filters for their project.  There is not a grid or list view of open issues to review. All items are in a card view. While this can be enough for some users, when my task lists get lengthy, I like to sort my lists by column headers. To be able to see a list view of the issue in a next-gen project, visit the issue navigator and filter for the project.
  4. Provide an option to hide completed tasks
    I like to have completed items fall off my backlog as time passes in kanban and at the end of a sprint in scrum to keep the workspace clean.  While the project is quick to set up and easy to add tasks – completed remain in view indefinitely. If a given project has a substantial number of tasks run through it, the completed tasks stack up on the board and in the backlog. The long completed list can make it very clumsy to manage the issues.
  5. Provide additional admin oversight
    Limit the number of next-gen projects or provide an approval process that admins can enable as needed. Many admins would appreciate this level of control to keep things clean.  As I work with companies, they comment on the speed and clutter in their Jira instance; I find many people have created a next-gen project to see what next-gen is, then they walk away from the project to create another later. The additional projects create “noise” for users and admins. While the effect on performance is not known, the noise leads people to perceive it as an issue and question me about it quite often.

Jira next-gen has some new and “reimagined” functions to allow individuals to kick-off and track their work with no admin support. Continued iterations could make the experience more intuitive.