As a leading project management and service management platform, Jira is always seeking ways to improve the user experience and increase efficiency. Even though your configuration might be perfectly in place, knowing what lies ahead will allow you to better plan and optimize your team’s work and projects. Whether your teams or process change, or you just want to better optimize your jira, check out the upcoming features listed below that Atlassian is planning to deploy — coming to a Jira instance near you soon 🙂
Use global custom fields in Jira’s team-managed projects
Expected: Q1 23
Platforms: Jira Software, Jira Service Management, Jira Work Management
Team managed projects have been designed to easily setup a team’s work flow. They contain all the needed ingredients for a tasks and project management, where the project owner manage the project’s configuration. With that, they were also designed to have minimal interaction with the rest of the system, and be self contained.
For larger organizations, this can lead to some trouble as the way that each project captures information might be different. Another issue is that fields are unique per projects. So, let’s say that 2 teams need to have a ‘budget’ number field, when coming to search for issues in the system, you will have 2 fields named ‘budget’.
with this coming feature, you could employ governance, where there will be a single budget customer field, that will be used in the team-based projects.
say goodbye to duplicate fields and hello to cohesive information!
Dark mode in Jira
Expected: Q2 23
Platforms: Jira Software, Jira Service Management, Jira Work Management
While i have already mentioned this feature in another article, it’s still worth mentioning. The full feature is expected to be available via a flag. Each user could choose their preferred display option. While it is currently in Beta mode, you could already start testing out the dark mode and see how it feels. I’m already using it, and while there are still bugs here and there and parts where it seems the designers/developers didn’t get to yet, the entire experience is very smooth and easy on the eyes.
Atlassian Data Lake for Jira
Expected: Q2 23
Platforms: Jira Software, Jira Service Management, Confluence, Jira Work Management, Opsgenie
Data lake and the Atlassian Analytics are going to be huge game changer for enterprises. In a sentence, you will now have the capability to easily connect data sources into Atlassian and present advanced analytics using pre-configured dashboards (or that you can create your own), which are drawing data from all facets of your work process.
To understand how powerful this will be, I’ve included a quick video (from atlassian.com)
I will also follow up with a series of articles about all the magic you can do with Atlassian analytics. To note, at least at initial stage of release, this will be available on the enterprise license level.
Multiple attachments in Jira Service Management
Expected: Q2 23
Platforms: Jira Service Management
I have received so many questions and seen so many raised eyebrows about this — Jira doesn’t allow to set multiple attachment fields??
This will soon change! Forms allow for a much improved UX experience for the end customers who open tickets on the portal of Jira service management. Smooth UI that allows for logic when presenting questions to customers, and now, the next step — allowing multiple attachment fields. Imagine that your customers need to submit hotel receipts, travel tickets and restaurant receipts. Now, each will have it’s own section and instead and allow for a better communication and faster resolution time on tickets.
It’s still unclear, at this time, if the separation of attachment “types” will remain on the agent’s view. I would assume that it won’t, and that this is only a visual resolution for the customer, but still, this is a major value booster.
Custom domains
Expected: 2023
Platforms: Jira Software, Jira Service Management, Confluence
I really love this one! It’s been longed asked for and it’s a terrific change, here’s why — Currently, all sites of Jira are set as X.atlassian.net. This doesnt play nicely with branding, and gives the feeling of working on something that is external to a company.
Beyond being a sign of inclusion for internal teams, working on Jira software and confluence, this is also affects Jira service management’s portal access! External customers will now use a domain that belongs to the business itself when they submit tickets.
Expect this feature to be highly utilized once it becomes available, and to be well guarded with safety measures! I do see this as being available to the premium and enterprise license levels, but we’ll know more once the feature starts it’s roll out.
Be sure to keep an eye as these updates, and many more, as they are rolled out the coming year. Use these upcoming features to streamline your team’s work and improve their tools! they will thank you for it!
