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

Question about Testing

Nikos Vlachos_gp6181

Hello Everyone,

I would like your help with a request I have.

The team wants a way to have a visual part in the Active Sprint to be aware when a task is retested for a second or third time. I did suggest introducing a Custom Field to be able to manually select the testing attempt.

But they are worried it will not be visible on the cards on the board. Any suggestions will be appreciated.

Accepted answers

Bill Sheboy

Hi @Nikos Vlachos

A few things to try, depending upon how much visibility you want. Hopefully this is a temporary condition which the team can improve, and so more permanent solutions may not be needed.

When this condition occurs, consider using right-click and flagging the issue. Those issue will then highlight in red on the board until the flag is removed.
Add a label, custom field, etc. to indicate this re-testing condition. And then add the custom field to the card's view for the board.
Let's say you want to automagically detect this condition when an issue moves backwards in flow from "In Testing" to "In Progress". That may be done with an Automation for Jira rule, setting either of the conditions noted in #1 or #2 above to make the situation more visible.
Lots of other alternatives, such as adding a comment and using quick filters, etc.

Kind regards,
Bill

All comments

Nikos Vlachos_gp6181

Bill Sheboy

Hi @Nikos Vlachos

A few things to try, depending upon how much visibility you want. Hopefully this is a temporary condition which the team can improve, and so more permanent solutions may not be needed.

When this condition occurs, consider using right-click and flagging the issue. Those issue will then highlight in red on the board until the flag is removed.
Add a label, custom field, etc. to indicate this re-testing condition. And then add the custom field to the card's view for the board.
Let's say you want to automagically detect this condition when an issue moves backwards in flow from "In Testing" to "In Progress". That may be done with an Automation for Jira rule, setting either of the conditions noted in #1 or #2 above to make the situation more visible.
Lots of other alternatives, such as adding a comment and using quick filters, etc.

Kind regards,
Bill

Nikos Vlachos_gp6181

Hello @Bill Sheboy

Thank you very much for your suggestion.

Since the team is already using flags for blocked issues unfortunately we are not able to use that.

I am curious about the 3rd option you suggested. So basically whenever it moves backwards we can either automatically comment or send a notification that it was moved to "In Progress"?

The solution I offered to the team was to add a Status of "Retesting" and then they will manually select that for the tasks they go for retesting and that will trigger the JQL in the Card Colours and will change the colour.

Bill Sheboy

Yes, with an automation rule you could add a comment/send a notification, set a custom field, etc. And many of those things could later be searched for using JQL. To learn more about automation rules, please look here to get started:

Your approach of using a separate status for this condition will also work, but it may have an unintended consequence: in my experience when a team adds an unusual condition to their workflow (such as "blocked" or "retest") they may be less likely to try to eliminate/reduce the occurrences. That is, the abnormal thing has become a normal part of their working methods.

Nikos Vlachos_gp6181

Thank you very much for all the information Bill. Will highlight that to the team

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud