nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tips on how to best use Jira for our project

Big Jim

Before we start in completly the wrong direction I was hoping that the community could advise how best to use Jira for our project.

We have a product that is tested for a number of years. There are various test types specified. Many of these test types will run in parallell. Each test type contains multiple individual tests which need to be assigned to individual team members. The aim in using Jira is to manage complex tests that take years to complete and are assigned to multiple users.

I have started defining issues and workflows but am not sure if we should use Epics, stories, sprints etc.

Thanks in advance for your tips.

Accepted answers

Christoph Schötz

Hey - I guess to provide better visibility for test suites you could use stories with every single test in a subtask or Epics with test cases as stories. If you use epics you can have test steps as subtasks under your test cases/stories.

Besides that I recommend you to start as simple as possible and look for the user acceptance and feedback you get before implementing things that will never be really used... How will users/testers look at their todos /tests btw? Will you use a kanban board?

Cheers

Christoph

All comments

Christoph Schötz

Cheers

Christoph

Big Jim

Hi Christoph,

Thanks for taking the time to answer and for your tips.

Unfortunatly I have to prepare a demo to be presented in 2 months so there will be litlle time for user testing and feedback.

Where I´m a bit stuck is how best to define a master test (description with prose description), the individual tasks related to this test for each team member (including technical details). This should be done in a way that I can clearly report the status of a master test (and all related tasks).

At present we are using Redmine and covered the above by simply defining invididual tasks linked to a test and the status shown by queries.

Again we will have multiple tests running in parellel for years so I am not sure if sprints are suitable ?

I'm also not sure if there´s some disadvantages of sub tasks (such as not being able to be included in sprints).

Sorry if these a vague or silly questions !

Christoph Schötz

Hi Jim,

You're welcome - I guess preparing a demo with epics and stories should take about 90 minutes for someone who has some JIRA administration experience - so I don't see why there is no time for testing and feedback?

You can give sprints any length you want to but it might be better to use fix versions for you.

Subtasks have indeed some attributes they share with their parent issue - I would use epics and stories first.

Cheers

Christoph

Big Jim

Thanks again,

Therein lies the problem. I am absolutely new to Jira and have been thrown in the deep end needing to immediatly define workflows and setup a demo project. After some struggling I have managed to create a new workflow and associate it with an issue type. How best to use epics and stories, tasks and sub tasks or even fix versions is not really clear to me.

Regards

Jim

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira