The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Inherit to the responsible of the "Bugs"

Alejandro Bermúdez
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 28, 2022

Hello Team Atlassian! 👋🏻

I am requesting your support, please.Currently, in the stories we assigned a responsible, but I would like be able to inherite the same responsible for the issue type through an Automation.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 28, 2022

Welcome to the Atlassian Community!

It's always a good thing to have a person responsible, that is exactly why the assignee field is there and is a single person.

I am not sure about the rest of your question, but it hints at having sub-tasks (part of the original issue) that help you break it up into more manageable bits.  Sub-tasks can have separate assignees, so my guess is that you are trying to work out how to (maybe create and) assign sub-tasks to someone?  Is that right?

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events