Would anyone be able to tell me why the field configuration is different between these two projects even though they're using the same screen scheme?
Hello @Jordan Trinklein
What you are looking at is an Issue Layout. Issue Layouts are not organized in schemes but rather are unique to projects. Refer to this document:
https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-layout/
"Issue layout settings are for individual projects. You can't share issue layout settings between projects right now."
These two Issue Layouts are leveraging the same Screen ("BW: Kanban Default Issue Screen"). The Screen determines which fields are available to show on the screen. The projects, however, can have custom layouts for those fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome.
If your question has been answered, please consider marking the Answer as Accepted to help other users find validated answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira is comprised of multiple schemes and these two schemes are different. Hence they can be different even if one is the same in a project.
I would recommend reading an article I wrote a while ago that goes over this as it should help!
https://community.atlassian.com/t5/Jira-articles/Jira-Project-Setup-Basics/ba-p/1614740
Best,
Clark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Clark Everson
Appreciate that article. My issue is trying to untangle multiple projects utilizing various schemes and workflows and configurations. It's a mess. I'm not sure how I'm able to tell those 2 projects are using different schemes, especially because those images show that the issue layout is for the BW: Kanban Default Issue Screen.
That would make me assume that they are both going off the same field configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jordan,
Jira is often a mess, which is why many companies end up hiring a Jira specialist. But in short no those ar eissue type screen schemes.
Field configurations are different, they control what fields can be edited, or hidden from them. Often times there are other ways to do that to. So while the two are related they are also separate. In reality all the schemes are related.
To be realistic cleaning up a Jira instance can take multiple years it's not a quick thing. I would recommend picking one thing to focus on and then only cleaning that, don't try and tackle everything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.