Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,552,139
Community Members
 
Community Events
184
Community Groups

Jira Sub-Task hide Fields

Hallo again,

we are currently working on adding sup-tasks to one of our projects.
Is it possible to add custom fields to the sub-task?

We have a Project called "Kundenkontakt" and a sub-task issue type called "Kundenkontakt Sub-Task".

I want to add a sub-task to "Kundenkontakt" with other fields than the parrent issue (Kundenkontakt). Is there a scheme or something similar?

 

Sorry for the question but Jira is still relatively new for me.

 

Best Regards, Björn

1 answer

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 12, 2015

Sub-tasks are mostly just seen in the same way as far as the configuration is concerned.

To have different fields for top-level and sub-task issues can be done in several ways, you just need to tell JIRA to use different schemes for the types.  I tend to do it with screens myself, but you can use field contexts and/or field configurations too.  For screens in your case, you set up two sets of screens - one to use by default and a second for the sub-tasks (I'd copy the default one(s) to make the sub-task screens).  You then change the fields on the second set of screens and then use the "issue type screen scheme" to tell JIRA "for sub-tasks use these screens, and for everything else, use the defaults in this project"

@Nic Brough -Adaptavist- 

I'm need something similar ... Steps I followed

1. Create a New screen

2. Added fields to this screen

3. Assoicated Scrren Issue Type and screen scheme

But still all the fields are display...

 

Am i missing any step?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 18, 2021

Associating the issue type screen scheme with the project I think

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events