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,342
Community Members
 
Community Events
184
Community Groups

Creating issue type which will have its own screen/fields

This seems like it ought to be straightforward but somehow I cannot get there.

Created new issue type called CR (for Change Request).

Created issue type scheme called Change Request, and it has a sub-task too.

On Issue type schemes page, three dots, associate. Selected the main project which has other issue types of course. Selected "associate". Then, I am viewing step 1 of 8 to MIGRATE other issues now into this CR and Subtask scheme. So, hit cancel.

Searched for answers, not finding any, hope you can help. 

Thank you!!!

2 answers

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 05, 2023

Hello @Tim Arthur 

A project can have only one Issue Type Scheme associated to it. If you are trying to associate a different Issue Type Scheme to the project then that association will result in only the issue types from the new scheme being available in the project. All issues of other types have to be converted to issue types in the new scheme.

If you want to just add another issue type to your project while keeping all the original issue types also, then you need to modify the Issue Type Scheme that is already associated to the project and add the new issue type to it.

You'll need to check if that Issue Type Scheme is used by any other project. See how this one says it is shared by 2 project.

Screen Shot 2023-05-05 at 9.30.59 AM.png

 

If the scheme is shared by multiple projects and you want to affect only one project, then you would need to make a copy of the Issue Type Scheme, modify the copy, and then associate the copy to the desired project.

Thank you. I guess we'll need to live with the fact of four fields useful only for the new issue type, will be present on the fields page for all issue types. 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 05, 2023

No, you don't have to live with that. I'm not sure why you think that is the case.

Perhaps you could explain what you are trying to accomplish in more detail, and then I can offer you advice tailored more to your scenario.

That'd be nice, thank you very much @Trudy Claspill .We'll keep this explanation simple. Issue type of epic, story, bug, sub-task, and cr (for change request).

It is ok if epic, story, bug, sub-task shares common fields, but would like for CR fields to be pared back to only, for instance: CR impact, CR review state, CR decision.

Hope that helps!

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 05, 2023

To change the fields that appear on screens for a given issue type you need to look at the Issue Type Screen Scheme and the Layout

The Issue Type Screen Scheme is comprised of Screen Schemes associated to Issue Types. Each Issue Type can be associated with one and only one Screen Scheme, but you can have multiple Screen Schemes, each assigned to 1..n Issue Types.

Here you can see I have two screen schemes; one associated to Bugs and one associated to the other issue types in my project.

Screen Shot 2023-05-05 at 12.08.07 PM.png

If you expand one of those you see the Screens associated with the Issue Operations for those issues.

Screen Shot 2023-05-05 at 12.10.00 PM.png

If you click through the Screen link then you can modify the fields that are available on that screen.

You can also modify the fields that display via the Layout option.

Screen Shot 2023-05-05 at 12.12.08 PM.png

 

The above both rely on which fields can possibly be available for the issue types in the project. The available fields are defined in the Field Configuration Scheme.

One Field Configuration Scheme is associated to a project. Within the Field Configuration Scheme, a Field Configuration (a list of fields) is associated to 1..n Issue Types. In this example I have one Field Configuration associated with the Bug issue type, and another Field Configuration associated with the other issue types.

Screen Shot 2023-05-05 at 12.16.52 PM.png

When you drill into a Field Configuration, you can change which fields will be available for the issue type that uses the Field Configuration.

If there is a field that you don't want to be available on a particular screen, find that field in the list and click the Screens link.

Screen Shot 2023-05-05 at 12.22.57 PM.png

Then uncheck the box next to the screen.

Screen Shot 2023-05-05 at 12.32.08 PM.png

The field will no longer appear on that screen.

Thank you. Will dive into soon.

0 votes
Himanshi
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 05, 2023

Hello @Tim Arthur , 

Welcome to Community !

If I understand correctly you wish to create a Issue type with it's own Screen and Fields. 

It is not feasible to create an issue type having designated associate screen and fields. You can create screen with designated fields associate it with the screen scheme and can use that screen scheme with the issue type from the project. 

From Project settings > Go to Issues >Screens> actions > edit screens > Associate an IssueType with a screen scheme > Select Issue Type and screen scheme and save it 

Let me know if this is what you were looking for ?

Have a great day !

Thank you Himanshi for your input.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events