I really need help with this issue. I need LOE to appear on the issue types for the project(s). The where is my field editor shows it is enabled and associated with this issue? See screen shot:
Hi Trena - I see this happen a lot when a separate Edit screen is setup and the field is not on the screen. It would also possibly be true that it is not in the view screen as well - but definitely check the Edit screen first.
John, I joined a team that had JIRA in place, but am finding that it needs to be cleaned up such as all all fields are pointing to the default field configuration and screens are going to default screen and labeled for each project.
I need a different field configuration for each issue type:
Bug< Task and Epic and different screen scheme. I have workflows in place that are allowing the issues to transition in the flow we want. But I am not able to get the screens to appears as needed. I believe this is why I am not able to see any fields needed on screens unless it appears on "every" screen? This is causing me huge issues. Can you tell me in a step format how to :
1. Create the fields and screens needed for each issue type
2. How to cleanly associate with each project as all projects will us the same issues and fields and screens
3. How to clean up
I believe if I had three screens :
epic
bug
task
and a field configuration for each I could then associate to all projects? As it is now there is a screen name but it all the same screen?
I feel if I could clean this up then I would be able to see the desired fields per issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will be happy to help with what I can. :-)
First you need to start with creating an Issue Type Screen Scheme. This is what will actually tied to the project.
The issue type screen scheme is made up of multiple screen schemes. Which it looks like you have created and ready to go.
It is under the Issue Type Screen Scheme where you will attach an Issue Type to a Screen Scheme.
1. So, create a new Issue Type Screen Scheme.
2. Click on Actions > Edit Screens
3. Click on Associate an issue type with a screen scheme
4. Select your Issue Type and link it to the appropriate Screen Scheme
5. Link the new Issue Type Screen Scheme to the project
Give that a go and see if it solves your problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, let me see if I can define the issue better.
1. We are using 3 issue types:
bug
task
epic
2, They are all tied to the default config (meaning I cannot make steps to reproduce required on the bug issue only. All the projects are set this way?
3. All projects have the same default field config, I need to have a different field configuration for issue type bug but when I try to associate a different field scheme it associates to all three issue type? I believe the issue is with the issue type all being tied together and I cannot figure out how to separate them for different field configurations
Because they all default to the default field configuration it doesn't seem to matter what screen scheme as the bug screen scheme is set to make the steps to reproduce be required but it is not working that way if I try it will make it required whether the field is present or not?
Your help is greatly needed and appreciated. Thanks so much for reaching out to help us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trena Norcia , the screenshot says that the field is not present in the screen you are viewing. Can you check in the create screen and the view screen of the desired issue types and verify that the field is there in those screens?
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.