What is the best way to go?

[Michael Zohner]

Hi,

we want to use Atlassian in order to create a good bundle for software development, testing, bug tracking and requirement engineering. I tried a lot and I think this would be maybe a good mix:

1. we created a sw dev project in JIRA for planning and tracking the features, dev tasks

2. we want to use JIRA to create a test platform (with test plans and test cases) - question: should we create a different project just to manage and track Test Cases OR should we use the Test Case issue type also within the above development project? What would you recommend?

3. We created a bug tracking project in JIRA with a typical bug tracking workflow - question: Is it the right way to use a bug tracker in addition to the test cases we will use in the above JIRA project or should we just use the test cases in above project OR the bug tracking project? What would you recommend?

4. We started also with Confluence (for our product requirements) to engineer all our requirements. We use a good template for each requirement and we built a good structure in Confluence at all.

The dev tasks the dev team creates in the JIRA sw dev project will always be linked to the specific requirements in Confluence.

Question: Do you think, this way to seperate requirements engineering, software development, testing and bug tracking is a recommended way? Or should we create a different structure?

What would you recommend?

regards

Michael

[Benjamin · Accepted solution]

Welcome @Michael Zohner . This is just my opinion but a lot of it will be driven by how your team works. So, you want to setup in a way to help your team boost their way of working.

1. Good.

2. In larger teams, you would want to use add-ons to have a proper test management tool on top. Especially, with large test libraries and versioning of test cases. Also, to keep test cases organized in central repository. For now, since starting out, you probably want to keep your test cases in another project to keep it organize. Then close the tickets you want to use into the project you want to test.
3. Best to keep your bugs with whichever the development project you are working to keep the bugs with the software that is being developed. 
4. Good practice. Documentation is very important. 

If it's one team regarding one product, better to keep things in one confluence space. So, teams can find all the related material to that app.

Since you are developing 3 apps, would have one space for each app.

Again, this is just opinion given the above context. Keep it simple and understand how your team works. The main thing is to help your team to find information efficiently and also to work in Jira and Confluence as simple as possible. Overworking the solution in Jira and Confluence can make it look very nice but make it difficult to work in. 

[Michael Zohner]

Hi Benjamin,

many thanks for your reply.

Its one big application which consists of about 10 modules, but it is 1 application (suite).

So, what I understood from your answer is:

1. ONE Jira project for development AND bug tracking (which means I have to add the bug issue types and also the bug workflow)

2. ONE Jira project for the complete test management (plans, cases etc) - I think I can link the test cases with the dev issue, right?

3. Confluence (business view) to engineer the product requirements 

Link all together (Jira issues <-> Confluence requirements <-> Jira tests).

Correct?

And, the bigger the product grows, we should add add-ons in order to manage dev and tests in a better way.

Regards

Michael

[Benjamin]

Welcome. You got this!

1. Yes

2. Yes, you can use the standard issue linking to do this.

3. Yes 

In a small team, keep it light and simple. As you grow and have more economic means, then buy more apps on top to enhance your teams experience. 

[Michael Zohner]

GREAT THANKS Benjamin!