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; } } }

should developer and tester use same sprint.

June_5gx9e7

we are adding the bug issue type. but we already have test management in JIRA with the sprint. when we create a sprint, should we discuss with testing team if we add the bug and related test cases to the same sprint or different sprint? same question as the business owner should create sprint with development team when creating requirements. does that mean developer and tester log in to the same project, but they are in the different groups. Are they going to see the same layout/same active sprint?

Accepted answers

All comments

Nic Brough -Adaptavist-

Possibly. It depends on your processes and how your people want to work together. Most important is your desired process, not "doing it the right way", but "doing it the right way for you"

Take a look at the life-cycle of a typical one of your stories, and what it usually should go through. Is it reasonable to expect that development and testing will almost always happen in the same sprint? Do the testers and developers work closely together so that a sprint could contain the issues? Or do you have two separate sets of people trying to manage their work separately?

If you do work closely together and can fit everything into a sprint, then yes, use the same sprint.

If you are more "developers code and fix, testers test on their own schedule", then use different sprints. Also consider using separate boards, which focus on one part of the process and workflows that cover the whole thing. For example a flow of

To do -> In dev -> Dev done -> In test -> Done

Might have a developer's board with a backlog that is "to do" and a done column of "dev done, in test, done". Then a tester's board would have "dev done" as the backlog, and "done" would be their done column.

June_5gx9e7

thank you for the reply. can developer see items/tickets assigned to testers although they are on the different boards.

another big concern is reporting that only shows done status, and testers are always the last one to close the ticket. developers' work are never being displayed on the report.

Nic Brough -Adaptavist-

Yes, people can see other people's issues, if the project permissions allow for it.

If you have one board, then there's no way to have anyone but the testers mark things as done - your definition of done is based on "has passed testing".

June_5gx9e7

thanks.

June_5gx9e7

Hi Nic,

i have another question for you, affects version: is that the environment that we found the problem? i.e. a bug is found in UA1 version 19. we are going to fix it in UT1 latest version 20. then migrate to UA1 with version 20. We may also need to fix this in UT2 version 3 which is the latest version for next release. UT1 is aligned with current production.

Thanks,

June

Nic Brough -Adaptavist-

Yes, most of us use "affect version" to record "what version we found the problem in".

June_5gx9e7

Thanks. is the version related to the environment as well?

Nic Brough -Adaptavist-

Not in Jira. If your processes need it to be, then you could add the environment name into the names of your versions.

June_5gx9e7

thanks Nic.

is phase detected a duplicate of environment or affects version ?

Nic Brough -Adaptavist-

No idea, that's something you've added and need to look at in the context of your processes. (By "you", I mean "your organisation has asked its admins to do this", not just you personally)