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: 

Avoid field inherit during subtaks creation (non numeric field)

Anette Noll
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.
July 18, 2024

Hello,

in a workflow I use various subtask (different issue types); all with their own schemes (screens, fields). Some fields apply to all subtasks, some are unique.

If I create/open the first subtask, all is fine. Those fields that apply to all the subtasks are empty (textfields) and I can fill it with content.
But in the moment I create/open the second subtask those fields that apply to all the subtasks show the content of the first subtask. I can overwrite it, but this is confusing for the users.

How can this be avoided?
I have seen this but it seems it is not applicable in this case.

https://community.atlassian.com/t5/Jira-questions/Avoid-field-inherit-during-subtask-creation/qaq-p/679485 

Thank you for your response.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Lígia Zanchet
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 23, 2024

Hi Anette

I was not able to recreate your problem. Is it on the create screen of those subtasks, are you using default values? 
If yes let me know and I'll try again internally to have more information 

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

Atlassian Community Events