Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automação raia de Teste Jira.

Boa tarde.

      Estou tendo dificuldade em automatizar uma parte do Jira, e preciso de ajuda se alguem puder ajudar desde já agradeço. Atualmente temos uma Raia com o nome EM TESTE em nossa plataforma no Jira, a intenção é automatizar ela da seguinte forma:

  • Quando o card for movido da raia EM ANDAMENTO para EM TESTE, este card deve ir para o nome do Tester do projeto.
  • O tester ao receber o card(na raia EM TESTE) e testar o mesmo deve enviar para a raia EM ANDAMENTO caso haja algo de errado no card ou para ITENS CONCLUIDOS caso esteja tudo certo.
  • O card deve sair do nome do Tester e retornar para o nome do Desenvolvedor que estava quando estava na raia EM ANDAMENTO em ambas as situações, quando o tester enviar para EM ANDAMENTO e quando o tester enviar para ITENS CONCLUIDOS.
  • Imagem das Raias:

automação jira raias..jpg

2 answers

Each person performs a developer or tester role.

Hi @Jucicleber Da Silva Gomes -- Welcome to the Atlassian Community!

How many different people are on the team for each roles you describe of Developer and Tester?

  • When there is just one developer and one tester, you could use an automation rule to set the Assignee whenever the issue transitions to a new status, hard-coding the person's user accountId value
  • When there are multiple developers and one tester, you could still use an automation rule and save the developer user in a custom field for later usage (when returning to In-Progress from Testing for rework)
  • When there are multiple people in each role, how do you determine who will perform the testing?  Once you can describe that, you could create an automation rule to make the assignments.

Kind regards,


yes every project has a tester.

Each project has about six developers.

Each person performs a developer or tester role.

Thanks for that information.

As I described above, you could solve this using custom fields to save the developer (or tester) when an issue transitions, and set it back as needed.  The saving and reset could occur with automation rules.

To get you started on creating your rule, please review this documentation and examples:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,797 views 37 48
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you