Jira Align Reviews

I have experience with these products. I have experience with Jira and ADO. You can ask me a few questions about my experience. I use it as an Application Lifecycle Management suite, but we are just using it for Agile software development.

I know Jira as Jira; I have used the cloud and I have used on-premise. It is an issue tracker.

My experience has been positive, as it is an okay tool, but I like Azure DevOps better.

I assess the dependency management feature as okay, but again, Azure DevOps is better; it is more customizable.

I find the scenario planning features are okay, but if you have a good Scrum Master or Agile coach, you can get a lot better insights just by looking at the data. We export most of what is in Jira to Power BI so we can run better reports.

I think it is probably better in almost all aspects over Jira; the dashboards are better, the filters or the queries are better, and it is more aligned to Scaled Agile.

To sum it up, the main room for improvement for Jira should be better queries and better dashboards; the queries cannot handle child-parent relationships very well. To do that, I need to extract into Excel and do VLOOKUPs, whereas Azure DevOps handles tree or nested queries a great deal better.

I think the customizable reporting in Jira is inadequate as well compared to Azure DevOps.

I have probably been dealing with it for about ten years.

When it comes to pricing, the last time we did pricing options, they were pretty comparable; it all depends on what sort of Microsoft licensing agreements the company has as to whether one is going to be better than the other.

I have not used Planview in a long time; when I used it, it did not really have the visualization or the features that it does now, as Mik Kersten created some really good flow metrics around that with his product.

I am more like a consultant.

If I had to recommend for companies, if there was an option on the table for both products, I would not; I would recommend Azure DevOps.

Some companies still choose Jira if they have Confluence or if they already have licensing and other considerations like that; sometimes it is hard to make a switch to Azure DevOps.

I have not been a partner or reseller of Jira; I have just been a consultant and a contractor.

I have not been a partner with Microsoft.

I left 2degrees a long time ago; I am now with Foodstuffs New Zealand.

I am using it right now to manage the project implementation with my internal teams.

Jira Align has become a standard in this industry, so everybody knows how to use it. Everybody knows Jira Align, so it is not hard to adapt to projects and customers. That is the aspect I appreciate the most.

It is very scalable, and I appreciate that.

Because it is a standard, as I mentioned, though not an official one, Jira Align is adapting to the latest approaches such as Scrum and Kanban. It is really easy to set up a project and start working with the team. Everybody knows Scrum, everybody knows Kanban, or a combination of both. That is the benefit I see, and the UI is very intuitive.

The way that you set it up presents challenges. The problem that Jira Align has is when you get it out of the box, all the configuration that you have to do is just a lot of work. A lot of work to get it to a point that makes sense to you.

The configuration is not easy. It requires a lot of customization from the admin perspective, and it is very time and effort consuming.

It is an easy tool to use but not an easy tool to set up.

The only challenge I have faced has been licensing because I depend on budget approvals. Besides that, it was very easy to scale, to add new projects, and to add new people. I have not had any issues on that end.

On Cloud, in all this time, Jira Align has failed only a handful of times. It is very stable. I have not been in a situation where I cannot use Jira Align for a long time, so I am very comfortable with that.

Jira Align is very scalable, and I appreciate that.

I have used the support team a couple of times in the past, and they were mainly for answering questions about the product. They were very helpful. They have a support knowledge base area on their website, and usually, they are very good at answering questions. I have had no issues so far. They are great.

Positive

My advice would be before getting a license from Jira Align or even starting to use it, they have to document their current processes, understand what is working and what is not working, and try to fix it before thinking about Jira Align. Use Jira Align when you have a pretty good idea of what you are trying to get out of it. This will save a lot of time, effort, and money.

On a scale of one to ten, I would give Jira Align a rating of eight.

Jira Align is primarily used in our environment to align our teams at scale and to connect strategy to execution, while ensuring teams are working towards achieving the same goals. It helps to determine the scope, roadmaps and dependencies easier and thus  accelerate enterprise agility and better business outcomes.

Jira Align has helped to improve provide more more optimized and predictable delivery with fully aligned organizations across every level of scale. It bridges the gap between business and technical delivery. Leading across the organization and innovation with agility.

AI is utilized worldwide; they could implement the functionality for notifications and other organizational operations in the product. It would be beneficial in planning, issues tracking, and setting reminders.

Our organization has around 200 Jira Align users working in different departments.

The technical support services are excellent.

Positive

The initial setup was a bit complex. However with the use of documentation we were able to successfully implement. I rate the process a 7/10.

Jira Align was reasonably priced then, especially for a bundle license that accommodated around 50 monthly users.

Jira Align supports program increment planning by facilitating the planning aspect, including team setup, dependency management, and defining the layout for each step or stage in a project. The platform aids in breaking down targets into parts, aligning with Agile principles, and ensuring a structured layout.

The most impactful feature of Jira Align for project management lies in its capabilities related to planning and setting up projects.

The platform visually understands targets, offering a clear and detailed layout. We can determine when to speed up the process or access the project. We can address the issues related to planning and development efficiently.

It is a great product to use, aiding in project planning and alignment. I recommend it to others and rate it a ten out of ten.

We use Jira Align primarily for IT service management (ITSM), including incident, change, and problem management processes.

One of the key benefits of Jira Align for our organization is its ability to help us maintain compliance with various regulations related to incident and change management.

The biggest advantage of Jira Align, in my opinion, is its user-friendly interface, making it simple and easy for end users to navigate and utilize. The most valuable feature of Jira Align for me is its automation capabilities, allowing us to create automation rules based on logical conditions for our projects.

In terms of cross-team collaboration, Jira Align's integration with our project squads has been highly effective. It enables seamless creation of stories linked to incidents and changes, facilitating better visibility and understanding of the relationships between them. Regarding road mapping and dependency tracking, Jira Align enhances our project planning by aligning with our best practices and providing robust capabilities for mapping out dependencies and tracking progress.

One area where Jira Align could improve is in its licensing model. There was a significant change in the licensing module about six months ago, which resulted in increased costs for customers like us. This change wasn't communicated clearly, and it made it challenging for companies to adopt Jira Align without facing higher expenses. In terms of features, I would like to see improved workflows in the next release, as that would greatly benefit our organization.

I have been using Jira Align for the last five years.

The stability of Jira Align is quite good, rated at around a nine on a scale of ten, with minimal issues occurring every six months.

I would rate Jira Align's scalability as satisfactory. While we are currently content with the capacity of the Jira products overall, we do not have immediate plans to increase our usage due to a freeze on projects during a merger and acquisition process. Approximately a hundred to a hundred and fifty users in our company, mostly from IT and some from business operations, utilize Jira Align. 

In terms of customer support, I would rate it around an eight. Although generally stable with rare issues, there have been occasional challenges with documentation, especially for certain modules like Apache.

As for the deployment process, it was relatively easy for us, and we had the assistance of a third-party service provider who guided us through the steps of setting up and deploying Jira Align.

The maintenance and technical support are handled by the service provider, Three Layer.

Despite this, the return on investment is rated at around an eight, considering the positive outcomes but also acknowledging the pricing imbalance.

The pricing and licensing costs are rated lower, around six mainly due to significant increases in licensing costs that were not well-received by users.

I would rate Jira Align as a solid product with room for improvement, especially in terms of licensing and pricing models. The rating is an eight out of ten. 

We have a group of several teams, each working within agile teams. These teams are organized into various solution levels, and we also have portfolio-level views that we manage. The product has facilitated alignment between our business strategy and all teams by enabling strategic planning and backlog creation at a high level. We've implemented lean portfolio management, which involves lean budgeting and brainstorming on various epics. These epics are then assigned to the respective value streams. 

Jira is one of the most widely used tools in the market, and it has a vast amount of data already stored in it. Jira Align is crucial in orchestrating this data and providing valuable views and insights. However, it's essential for tools like Jira Align to offer configurable features. While complete customization might not always be feasible for enterprise-level tools, configurable features allow organizations to drive transformation accordingly. 

The feature I've found most valuable for improving my team's productivity is the Gantt chart view. It helps organize our backlog and track our progress toward achieving our goals. Additionally, the ability to connect dependencies within the tool has been very beneficial for us.

Jira Align offers a one-stop solution for managing projects and platforms. However, its biggest competitor could arguably be considered an Excel sheet.

I've encountered limitations in using Jira Align for certain aspects, particularly in implementing OKRs. Jira Align's highest hierarchy is Epic, which may not always align perfectly for specific initiatives. Additionally, while Jira Align offers functionality for tracking OKRs and generating dashboards, I've found that it lacks in some areas. As a result, we've explored alternative solutions that better meet our needs in these areas. Its Kanban feature is also limited. 

I have been using the product for two years. 

The tool has been stable since we moved to the cloud. 

Jira Align is highly scalable. The number of licenses purchased primarily determines its scalability. As you buy more licenses, the scalability of the tool increases accordingly. 

The number of users using the product varies depending on the organization. For example, at one client, there are approximately 250 users, while at another organization, there are around 550 users.  I haven't had the opportunity to work with organizations with thousands of users.

The tool's setup depends on the user's familiarity with the tool. It may seem intuitive for individuals with extensive experience using Jira, like myself, after sixteen years of usage. However, Jira can appear daunting for newcomers, akin to navigating an ocean. Deploying Jira effectively requires expertise and support, ideally from external consultants who can guide the implementation process. 

While external consultants can provide expertise, having knowledgeable individuals within the company who can guide its use is also beneficial. Companies often rely on employees with experience to make changes and manage Jira Align. Many companies have complex workflows that may not be optimized, leading to challenges in effectively utilizing Jira Align's capabilities. I name this scenario growth pain. 

Our customers buy licenses. We are not involved in its purchase. 

The reporting analytics feature in Jira Align provides valuable insights into our job processes. However, it's important to note that while analytics can offer perspectives based on the data we input into Jira Align, it's just one aspect of how organizations evaluate success.

Organizations also require insights into revenue realization, overall throughput, customer satisfaction (NPS), and other metrics that may not be directly captured in Jira Align. Therefore, while Jira Align's analytics tools work well within their scope, a broader perspective necessitates integration with business intelligence tools to gather insights comprehensively across the organization.

I rate the overall product a seven out of ten. I would recommend Jira Align to others, and I have some advice for those who want to start using it. My advice is directed more towards Atlassian. They should focus on being more empathetic and creating awareness about Jira Align. It would benefit them to allow people to use Jira Align for longer to experience its full potential. Understanding the diverse perspectives of different user groups, such as business, product, engineering, and infrastructure teams, is crucial. Atlassian should consider a wider range of personas and conduct deeper inquiries to address the various needs effectively. This approach would help establish Jira Align as a trusted partner for users. If I were to rate Jira Align as a trusted partner on a scale of one to five, I would give it above three. 

I mainly use Jira Align to manage my software development tasks for Apache. It helps me create user stories, organize tasks, and set up test plans and cases, making the whole process more organized and efficient.

The most valuable features in Jira Align are the dashboard for tracking my team's work progress, which helps me monitor story movement, and the reporting feature to track time estimates versus actual work done. This reporting is crucial for sharing project progress with senior management. I also find the integration with various testing tools essential for ensuring proper test case management and traceability.

One area where Jira Align could be improved is mobile accessibility. Right now, it is mostly for laptops, but it would be more user-friendly if it had a mobile-friendly interface. This way, senior management and others could easily check progress on their mobile devices when they are not using a computer.

I have been using Jira Align for almost five years.

I would rate the stability of the solution as a nine out of ten.

Jira Align is highly scalable. I would give it a ten out of ten for scalability. In my company, we have about 600 users of Jira Align, and we plan to expand its usage in the future. These users include engineers, team leaders, and architects. The majority, around 60%, are engineers, while the remaining 40% are in leadership or higher-level roles.

I would rate the technical support as an eight out of ten.

Positive

I would rate the easiness of the initial setup as a seven out of ten.

The pricing for Jira Align is quite high, especially when compared to Azure DevOps. While Jira Align has more features, the cost is a major concern for my organization. As a result, we are thinking of switching to Azure DevOps because of the cost, even though it offers fewer features. I would give it an eight out of ten in terms of costliness.

My advice to those considering using Jira Align is that it is a valuable tool for project management, especially for handling large-scale projects. It offers scalability and is relatively easy to manage and customize to your specific needs. It is a good choice for project management and agile practices. Overall, I would rate Jira Align as an eight out of ten.

We are primarily managing larger portfolios. In this case here, I'm currently with a bank and this solution is used for larger portfolios of initiatives that are current within the bank. From there we're determining the course of action as it pertains to the work that is then performed by the individual departments.

Before we had no ability to even manage projects that we ran in Jira. These are software projects, including infrastructure work, and now everything is happening in one tool. The ability to use Jira Align now to bring these projects into a common portfolio is something that we otherwise had to do with spreadsheets prior to this.

There’s definitely the ability to manage larger initiatives that go across multiple projects. Otherwise, Jira in itself does not allow you to go across projects. You really have to manage several projects, however, you have nothing that aligns with them. You have to have Jira Align on top of Jira to have that capability.

The initial setup is very straightforward.

Maybe some of the terms and the connectivity could be improved. Jira Align in Jira, they share common fields in order to be aligned. These could be improved. Sometimes alignments are missing or they just disappear and we have to reestablish them.

I’ve been using the solution for two years now.

The solution is stable and reliable. There are no bugs or glitches. It doesn’t crash or freeze. The performance is good.

So far, the solution has been quite scalable. We haven’t had issues in that regard.

In our organization, Jira Align users are limited to about 25 people. In the case of Jira users, there are about 300, roughly.

There are plans to increase usage. It is, right now, used across most of the organization, although the teams have not adapted all processes, all Agile processes, yet. There will be continuous improvements as we go forward.

We’ve been very pleased with technical support so far. They have been helpful and responsive.

I also use Rally Software.

Similarly, since Jira and Jira Align are more intuitive., we prefer them Particularly, Jira is more widely used than, for example, Rally. Blueprint was a niche market product that really covered different aspects of the work. In this case, how do you manage individual documentation that you want to manage as part of a single project? That would be an enhancement to Jira, for example. Rally simply was just less intuitive.

The initial cost, particularly for Jira Align, appears to be higher. In the end, even Rally did not offer all functionalities unless you were including other products that were needed to perform the same function, therefore, the cost became equivalent.

The initial setup is very simple and straightforward.

I was not directly involved in the deployment and therefore can’t get into how long the process took or what specifics were involved.

The solution, in terms of maintenance, is handled outside. It is a fairly small team of maybe five people.

The setup was done in-house with the assistance of a vendor.

Overall, we're satisfied with the process. We did have some scenarios where work was assigned, where work was aligned with an individual's account, and when that person left, we were not able to access that one. However, that was more on the administrative side and those were unknown facts to us at the time.

We’ve seen an ROI. Since we prior did not really have a good solution and even prior solutions, were much more complex and less intuitive. When we used the product, we definitely saw an improvement. Some of the work continued to be managed in spreadsheets, which are now maintained in a single set of tools. We definitely saw at least 20% to 30% in work experience improvements, time management, and the simple ability to reduce waste time due to generating reports. Externally updating spreadsheets, we saw a lot of improvements in the way how we operate.

I don't have the licensing cost, however, I know Jira Align is much more expensive than Jira. I don't have the numbers as I don't know what the enterprise agreement is.

The operating costs would be there still, as you do need a team that has a general understanding of the application so the operational cost has to be included when considering what the total costs would be.

We are using whatever the latest version of the solution is. I don’t know the exact version number. We managed it as a SaaS. It’s managed by a vendor.

Jira and Jira Align are for larger development organizations and organizations that need to manage the portfolio work in a single tool are definitely a viable option.

I’d rate the solution eight out of ten. If you were to compare the solution with Rally, I’d rather use this and Jira together.

We generally use it for reporting. It's to have transparency, to get to the incremental values. We do have value streams built up on Align and we get the metrics, how the program works, or the dependencies, not just between the teams, between the programs, or between the portfolios.

What you have in Jira are the scalability and the agile approach. It's all about getting to all the stakeholders or the enterprise users so that they can see what is happening from the bottom to the top or from top to bottom and how it's happening. 

When it's all other agile tools, you could just view what each team is doing, and how the work is delivered within the team. However, it is going above and beyond the teams. When you are doing a scaled agile, when it all involves the whole enterprise, you use the Jira Align. It's a combination when you try to do the scaled agile combining the teams, combining the programs, and combining the portfolios, that is when the Jira Align is of most use.

We use Jira Align on top of Safe 4.0 right now. They're not supporting Safe 5.0 yet, however, they are using it as VR; I used it on top of the framework as Safe 4.0.

We brought it for a very big program. Before that, everything was all silos. The teams were independently working and there was a lot of dependency from one team to another team, which was either tracked in Jira in the roadmap, and it was all over the place. Once we bought the two and tried to combine the teams, depending on what their objective is or what they're working towards, combine the teams and make them into our programs and combine the programs and make into our portfolios, what we saw was a huge value-add. It was transparency. You could see the vision, and the transparency is what was the most beneficial thing - that, and dealing with the dependencies.

.For example, if you have so many teams working towards one goal, not everything can be understood, done in silos. You have to group them in a value stream so they can work towards that one value, and even when they're working towards that one value, you would see a lot of dependencies between the teams and between the programs. Managing that and delivering that on time is what when we push it towards a scale agile with the Jira Align as the thing that holds everything together is what we saw most beneficial

Of course, after that, you would get further enterprise agility, business agility, et cetera, when you start using it more and more.

The objectives are good. If you do use a scale agile, the concept of moving objectives and moving your team's work towards the objective is what is going to give you the most value. You plan around the program increments. That's what the program is about. You plan around the program increments, you do the inspect the workshop, you do the retrospective and all those things. However, for example, when a stakeholder doesn't understand the feature, or they don't even care about it, yet they have an objective or a theme, they move towards it. It makes the objectives very clear, and very obvious.

When you try to move work where the stakeholders know what it is and what they're moving towards, at the same time, when you break down the work, the team can understand what they're working toward. A program manager would understand what they have to deliver in a particular timeframe. That kind of split, you could see. There's great visibility there. 

I really appreciate that Jira Align gives the concept or the functionality of what is called a work tree or a roadmap, which brings it all together and gives you a view of what the company or team is moving towards and who is contributing to what. The OKR experience is great.

There are fewer customization options in Jira Align due to how it was designed.

For example, in Jira, you can combine stories and you can create an epic. However, in Jira Align, they combine the stories and call them features you can combine features and call them capabilities. You can combine capabilities and call it epic. It's structured differently from Jira.

You just cannot buy Jira Align and just started using it. You can, however, the most beneficial thing comes when you start using Jira, and then integrate it with Jira Align, and bring in all the work done together as the actual work is done in Jira, and Jira Align is just a representation of that work.

It's the naming convention that everyone is struggling with. Jira is more widely used and has a bigger customer base. They shouldn't change the terminology if people need to use Jira in order to get the most out of Align and then have the two different naming designs. It's very confusing.

The UI needs work. We are part of the pilot team who are testing the new UI. Jira Align is trying to change the UI so that it is just like Jira. We didn't like it as the UI makes the functionality kind of change. If you have never used Jira Align and you are a brand new customer who used Jira, the sales pitch would go better.

There are lots and lots of reports and it's very hard to understand exactly how we can use all of them. It's quite dense. They need more documentation.

I started using the solution in 2020.

They have done a lot of work fixing bugs and making all types of enhancements. They are working to make everything more functional for agile. 

The stability is very good. Our company was very mature and they have 800 programs in it and ten big portfolios. Jira Align does handle everything with no issues. We don't often have big performance problems. However, for example, if you try to load the roadmap for one big portfolio, it does take time. That is understandable as it's loading huge amounts of data. Other than that, it is actually good.

It is very good at scalability. It's not complete scalability, however, Jira getting integrated with Jira Align is great and it scales that way. If Jira Align is open to getting integrated with other team levels, and managing the work tools, then it would be easier. Right now, to use the Jira Align, either you have to use it as a silo, or you should have Jira in the backend. You cannot have other tools. A lot of enterprises would have other Azure tools or Microsoft tools, from which they manage the team's data, and they would be hesitant just to move to Jira Align as they are using some other tools which cannot be integrated. 

Right now, we have more than 5,000 users on the solution. On Jira, we likely have more than 20,000 users. Not everybody needs to be on Jira Align. It is being used extensively, however.

The support was good. They recorded all of the training sessions, for example. They really helped us learn the tool early on and were very supportive. 

In terms of ongoing support, we do have weekly calls where we go over support tickets, issues, bugs, et cetera. We have regular productive TAM meetings. 

Positive

We did not previously use a different solution. 

I was not part of the deployment. That said, looking at it, it seems to be very user-friendly and would not have been a hard setup. I'd rate it a four out of five in terms of ease of setup.

The deployment took more than two months. It's not full-time and we didn't rush through it. We didn't do it enterprise-wide either. We had a lot to consider and we were being strategic. Likely, if you were aggressive, you could do it in a couple of weeks. For us, bringing in the scale agile concept did take a lot of time. Once we figured that out, there was just connecting and creating and mapping the states and all of that was pretty straightforward. There's pre-work to be done, however, it's worth it to take your time. 

We do have a solution architect from Atlassian that helped us with the setup. It wasn't a hand-in-hand implementation. there were training sessions. 

The person who helped us and ran the training was very supportive and very pleasant to work with. What they taught us via training was about Atlassian, however, the setup was so specific to our company, that without having an extensive background in our organization, they really didn't have the capacity to go beyond training. We'd have questions like "what if we did this, or that?" and they would have to circle back to a program manager to get the answers. That said, they did cover all of the topics. 

I can't speak to the exact pricing. 

We are customers and end-users.

We are using the most recent version of the solution. We're using an enterprise edition cloud.

I'd advise users, if they have Jira, to just go for Jira Align. Just start off with a small number of full licenses. You don't need to have a lot of full licenses just to implement Jira Align. With us, we could actually see what's happening in the organization. The silos disappeared. People can see deliverables and objectives more clearly. It helps bring a lot of motivation.

I'd rate the solution nine out of ten, having never used any other enterprise agility tools.

We use Jira Align for business strategies, collaboration, and reporting. The solution allows us to manage the various products and features delivered on that platform.

We use Jira Align for business strategies, collaboration, and reporting.

I have been using Jira Align for over seven years.

We are quite a big organization, and hundreds of employers use the solution in our organization.

I've not faced any challenges with the solution's configuration and initial setup.

Jira Align has price packages for different purposes. Users must do their own research and see if it fits their purpose.

Users have to understand their business objective before using the solution. Given the right training, it is easy for somebody to learn to use Jira Align for the first time.

Overall, I rate the solution a seven out of ten.

We're creating a centralized place for our stakeholders and sponsors to have shared access to project details. 

My partners are normally the architects, engineers, and product owners. I work as a senior project manager and program manager. I have the scrum role added to me when we don't have any since I'm a scrum master too. I've been on the engineering side as an engineer, like onboarding and monitoring and creating all the meetings, and meeting with our customers more. I'm able to use Jira to help facilitate tasks related to various projects.

It's easy to set up.

The solution is user-friendly, and it's very easy to use once you go through the guidebook. There's lots of great documentation. 

We can integrate with other solutions, like Azure, GitHub, Slack, et cetera.

I am really focused on identity access management and getting access to the vendors. Right now, I'm setting up vendor access through Azure. You can do that or with the IAM.

Sometimes we have to create several different types of access because we have vaulted databases. We have the Unix databases, I have MySQL, and we have Mongo, where I get access to those user classes or to the databases in the host group. Those are all different access scenario forms that I submit after I do the configuration in the form with the security team. I need clarity on the IAM.

I'm not clear on PAM eighter. Is there a form that they have to submit to get access to the internal cyber-risk teams to get their access for people to be able to use the tool on the Confluence side? Do they have to send some kind of form to the operation's security or enterprise security? To be able to get the access for privileged access, do they need to be working on projects that have vaulted databases? I still need to figure out how that works. 

Other companies that are competitors of Jira and Confluence, are able to create their active directories for the vendors that don't come in internally. They only do access through the cloud and through third-party, two-factor identification. That's something I was wondering if that was already implemented in the packages, the package for Confluence. It would be nice to have that right in the solution.

I've used the solution since 2016.

The solution is stable. We use it with GitHub a lot and it works fine. 

I basically have never had to deal with support. I've only internally asked for assistance. Usually, it's the Microsoft person or whoever the administrator is. We use Slack or Microsoft Teams that are interfaced with those tools as well, and when we need help, we go through those solutions.

We have it all in a channel where we customize our teams, and then we have all the channels for whoever we need to reach out to for Atlassian. If we have Jira Confluence or Azure issues, we just reach out to the Microsoft person, one guy we all know can assist.

We were trying to use Microsoft Teams to centralize everything. However, we only track our actions and our action items, and our issues and risks.

Microsoft Teams now does have a template I create through an Excel template I upload. 

I usually managed only the Jira side, not really the Microsoft side.

It's pretty simple to set up and start using the solution.

Usually, I go in and look at the functions and options, and usually, I create my project teams more in Jira and Confluence as well. Then I start creating whatever epics I need. I start creating my boards, what we're going to create, to my backlog first and then the parent, the backlog, and the sub-criteria. I'm not really working with these tools on all my projects since not all of my customers are working with these tools.

I pay for the service every month. 

I only get billed for the services I use. I don't know what it costs internally from a corporate perspective, as it has to be used when they buy the package itself. Therefore, I don't know the cost from a corporate perspective, I only know from the way I use it. I just purchase the licensure, and then they bill me directly and invoice me monthly.

I've been getting invoices since 2016, and I started off at a higher cost, and now I find the price to be lower. 

I have it on my phone. I'm doing testing. With Jira, you get billed when you're working as a freelancer or a consultant. I get billed monthly as an invoice, so I have to go and test their new functions and features monthly. When you have the licensures, you must touch the application, the system.

If you're used to working in GitHub or when you're working with engineers, they tend to have their own version one tools. Jira is good for working well with GitHub and has been since the beginning. Jira has gone ahead and created functional user roles for each user that is going to use the tool.

Potential users should understand that they have options. 

I had someone demo everything with me back in 2016. And then, I had someone demo the updated features for Trello. They can really dig in and show you some interesting features. Learn the business side, the process side, how to use it, and what it can do, and you'll be better off when you start.

I love Jira and Atlassian products. As a matter of fact, I promote them. That said, I'm also promoting all of Azure and Microsoft and your products as well. I'm taking the training for both Atlassian and Azure for the cloud. Right now I'm doing all of the certification training right now. 

Make sure that when you're using the Jira side, that you're using Jira for the backlog and creating the product. In Jira, we create the product backlog and the backlog for prioritizing the work we're going to do. Then for the Confluence side we assign to an administrator that manages the site period, the platform's governance that provides the access to all of us. That's more the Confluence side.

I use Jira more for managing projects or creating the product charter. 

Then we implement all our artifacts and documents in a centralized place. We add our iterations. 

Everybody needs to use Jira always on their projects. I'd rate it ten out of ten.