Implement JIRA in a large company

I am considering setting up JIRA for my current client. It will be used initially as a defect repository, then possibly moving a boatload of spreadsheet based scripts and requirements in there.

I could do with a bit of advice on how long it’s taken people to set up JIRA in the past.
Any tips and pitfalls would also be helpful.

Don’t overcomplicate the transitions flows. Keep it simple
Use the default settings in general, make sure you setup projects, components etc the way they should be
You can automate alot of things, check the Jira API
If you’re planning to integrate that solution with your stuck anything Atlasian is easier to set up

Thanks for that. It’s along the line of my thinking.

Amusingly, it turned out that my client had a JIRA instance set up already. It just wasn’t broad public knowledge.

I can drill holes with a manual drill but I’m going to be more efficient with a power drill. Switching from a manual drill to a power drill does not change the fact that I’m a skilled carpenter.

The same holds true for JIRA. It is a tool. The people using JIRA should already have processes and procedures for how they do their job. When I teach Kanban, XP or Scrum I don’t use tools like JIRA. I might use a physical wall and index cards. Once the team knows how to do the work, we introduce tools like JIRA to make it efficient. How we configure JIRA depends on how they are going to do their job. So understanding how the team does the work is key to how to configure JIRA.

JIRA is highly configurable. There are many third party plugs which will make it more efficient. You just want to avoid having the tool define (or re-define) how they do their job.

The biggest danger of JIRA is that it is highly configurable. The second biggest danger is not paying for third party plugins. Sometimes the out of the box JIRA doesn’t do exactly what you need. You can make it but it is sometimes easier to buy a plugin rather than spend weeks trying configure the basic JIRA.

1 Like

Before implementing any paid tool in an organization, we should get proper knowledge about the same. Jira is a paid bug tracking tool which is developed by the Australian Company Atlassian. The main purpose of this tool is Project management and to track Bugs, Tasks, Enhancements etc. This tool can also be used for time tracking on assigned tasks. We can also pull reports related to defects reported, defects regressed, time logged etc. One of the good advantage we can check the current status of any bug/task (For example: In Dev, In-Test, Ready for Test etc). Now, member (Dev/QA) can be aware which team needs to work on which particular ticket.

Many functional testing services companies wants to implement Jira because it have the ability to promote and develop Lean & Agile principles, which benefits in saving time and money. Jira experts can show and make use of everything from knowledge sharing and asset tracking to all the workflows and add-ons helping us to streamline our company’s digital and development operations, which is a huge plus.

Jira has many features to offer than other project management tools in the market and it has the capacity to be customized to meet any business needs in the real time environment. Jira contains multiple Plug-ins, which allows the system to automatically generate sub-tasks for items that need to be complete on every single Jira issues. We can also create sub-tasks for unit/integration testing and technical documentation.

Jira keeps the transition and workflow pretty simple. Hence, we should implement Jira in the large business or company because of its vast features. Hope this information is very useful for you.

Coming from a user’s perspective, JIRA can actually be really convoluted. Sometimes I do find myself having to do a lot of clicking around just to get to one page.

I would suggest that you trial the set up and configurations you like yourself before rolling it out so you are all on the same page with how it works.

We use JIRA in my current place and have integrated it with Salesforce, Toggl, TestRail and it is great if you want a “in-all-one-place” product though.