nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom field order not being reflected in projects

Kaitlyn Hoban

Issue is: custom fields and field order are not being populated across projects that have the issue screen scheme assigned.

Workflow, field configuration and screens have all been assigned accordingly. I'm able to verify through the Project Settings>Summary>Screens that the screen assigned is there and when verifying the screen scheme the order and fields needed are there. Once out of the project settings, the project doesn't reflect the fields nor field order that project settings showcases. Out of the near 15 issue types that can be created for this project, only 2 are having this issue Project and Bug.

Thoughts?

Accepted answers

All comments

John Funk

Hi Kaitlyn - Welcome to the Atlassian Community!

Yes, the screen will have the base set of fields available and you can put them in the order you want. However, there is an Issue Layout view for each project for each screen that can be changed by project administrators for the project. So just because the screen configuration has a certain order and is used by multiple projects, the order of the fields can be changed by project to be different.

To see that, while on an issue, scroll to the very bottom right of the screen. You should see the Configure link. Click on that and you can see that you can change the order and where on the screen the issues appear.

Kaitlyn Hoban

Hi John! Appreciate your advice. I'm with you, scrolling to configuration is where I can change the fields on this project level basis, but I have the issue screen schemes attached to specific fields so the field order can be managed on a more global level. That is where i don't understand why these two types of tasks out of 15 are not following their assigned issue screen schemes. I can confirm that no administrators have altered the order of the fields on the individual project level basis. So they should in the order of the issue screen scheme

I'll attach a few screenshots. One of the individual project view, which indicates what issue screen scheme the issue type is assigned. and then one of the issue screen scheme itself. You can see they don't match, neither the type of fields nor there order. I'm not sure where its going rogue.

First image is the individual project configuration screen. showcasing what screen is being used for Epic

Second image is the issue type screen scheme that is titled IT-Epic Screen.

Johan Hansson

Hi,

Any update on this one? I have the same problem as Kaitlyn that I want to define an order of the fields for the screen so the same order populates for all projects using that screen. How do I do that?

John Funk

I guess better late than never, right? So sorry that I never saw the email with your response - I was out of action during that time for a couple of months.

The question would be how can you be sure no one altered the order? Because they said they didn't? You can't trust people's responses like that. Also, it can be a project admin or a Jira Admin who can make those changes.

Regardless, you just have to set them back and monitor it for a while to see if it changes. But the system itself will not rearrange the fields on its own.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud