Jira in your company: an implementation guide for non-IT teams

Many guides still describe three separate products: one for developers, one for business teams and one for handling requests. That is out of date. In May 2024, Atlassian merged Jira Software and Jira Work Management into a single product called Jira, with templates for developers as well as for marketing, HR or legal.

In practice, a mid-sized company now chooses from the three elements described in the table below. In the newer version of Jira, projects are called spaces, so do not be surprised to see that word in instructions.

Jira moves work through defined stages: request, analysis, approval, delivery, closure. Every status change is kept in the history, and rules can, for example, require an amount to be filled in before a request is passed on. For a department that needs order and a record of decisions, this is an advantage.

For a team that works informally, the same feature can be a burden. The signs below will help you judge which side your department is on.

The uses below suit Jira well because they follow a repeatable path and need a record of decisions. The first three are usually handled in Jira Service Management, the rest in Jira itself.

Take a hypothetical trading company with 150 employees. Employees submit requests to HR through a simple form on the portal, and every request goes into a single queue with a response deadline. After a quarter, the HR manager can see what employees ask about most often and can prepare instructions that reduce the number of questions.

Atlassian publishes prices in US dollars per user per month. The amounts below come from the October 2026 price list and apply to monthly billing. For annual subscriptions, Atlassian uses user tiers, so calculate the exact amount with the calculator on the vendor’s website.

Take a hypothetical company in which 50 people work in Jira and Confluence and 5 people handle employee requests. Jira Standard is 50 × USD 8.48 × 12 months, or about USD 5,090 a year. Confluence Standard is 50 × USD 5.78 × 12, or about USD 3,470. Jira Service Management for 5 agents is 5 × USD 21.50 × 12, or USD 1,290.

In total, licences come to about USD 9,850 a year. On top of that come implementation work, training and the time of the person who will administer the tool.

For a company working in Microsoft 365, what matters is that people do not have to live in two worlds. Jira has official apps for Microsoft Teams and Outlook. Employees get notifications in Teams, comment on a task without opening Jira and create a request from an email.

The biggest difference concerns documents. Atlassian assumes documentation lives in Confluence, while companies working in Microsoft 365 keep it in SharePoint. The two can be reconciled: a link to the SharePoint document in the Jira task is enough. But you need to decide up front what goes where, or people will look for instructions in two places.

Jira can produce reports for the management board itself, and in paid plans Atlassian’s AI assistant, Rovo, helps with this. If the company’s reports are built in Power BI, the Jira data has to be brought in through a connector or add-on, which requires extra configuration.

Rolling out Jira for a few dozen people outside IT usually takes 8 to 14 weeks. The exact time depends on the number of departments and integrations. A shorter timeline usually means a configuration that nobody has tested on real work.

Start with one team that has the simplest workflow, most often HR requests or internal IT support. Bring other departments in only once the first one is working in Jira day to day. A sample plan looks like this:

The most common problems do not come from the tool itself, but from how it was configured. Each of the mistakes below can be avoided at the planning stage.

They all have one thing in common: the configuration should serve the people who work in Jira every day, not the person who sets it up.

Today Atlassian is developing mainly the cloud version. It has not sold the Data Center version, installed on the company’s own servers, to new customers since 30 March 2026, and support for it ends on 28 March 2029. So a company starting with Jira today is in practice choosing the cloud.

In paid plans from Standard upwards, you can choose the region where your data is stored, for example the European Union. Atlassian also publishes its security certifications, including ISO/IEC 27001, in its Trust Center. Before buying, it is worth having your data protection officer review the data processing agreement and the list of Atlassian’s sub-processors.