I have not added Priority,Resolution,Labels fileds to the createIssue screen even though they are displaying after creation of issue.Requirement won't show this fileds after creation of issue.
For those asking the question again recently, the answer remains "Hide priority in the field configuration"
If it is not hidden in the field configuration, then it will always appear on issue view, even if you remove it from all the screens. Because if you don't hide it, then you need it. But only if it has a value (so if you remove it from all create/edit/transtion screens, then the users will not be able to set it to anything)
@suresh ... Check the field configuration associated to your project .. identify the screens and recheck if the fields are there .. The fields wont appear if they are not on the screen .
Also confirm if the resolution field is to be removed ... Or you can have the resolution field only on the resolution screen
I assume you wanted to post a screen shot?
Could you at least tell us what version of Jira you are using, where the fields appear when you look at the new issue. Check your screen schemes (check you are looking at the right "view" screen) and field configuration schemes (are you sure you've hidden the fields for that project/issue-type?)
(By the way, you've said "Even in field configuration also those fileds are not associated to screens." which is nonsense because field configurations are not linked to screens. That's why I ask you to check everything carefully)
While creating an issue i don't have fileds Priority,Resolution,Lables.
After creation issue: Priority,Resolution,Lables is filled with default values.So for the requirement it should not shown those fields.
No i have not hidden the fileds for the project/issue type.Because those should be coming in resoultion screen or workflow screen.So if user selected the values to this filed then it should be show.
Did you get a solution for this? I need to remove the Priority field from my Screens. I have removed it from the Create, Edit and View screen of my project. While creating, the Priority field is correctly not displayed, but once the issue is created, it is visible on the Issue View.
You would need to have a couple of different field configurations, one that has priority, one that has priority hidden.
I would not hide the resolution field as too much of JIRA depends on that. Labels, priority are fine. You could have a workflow that sets the resolution when the issue is closed so you don't need to give your users the choice
Also, one of the project reports "Unresolved: By Priority" shows an error if you hide Priority I seem to recall
ugh, I did eventually figure out what @Nic Brough [Adaptavist] was saying about hiding the field instead of just removing. I had never done that before. I will say, however, that it did work on hiding priority field from issues but not from Kanban agile boards. It still shows there. Any way to remove it from there as well?
For this wondering about removing the field, try this: #.atlassian.net/secure/admin/ViewIssueFields.jspa and then hide priority field, then reindex
also, from Atlasssian, not a bad workaround that works "Since "Priority" is a System Field and is required, I would recommend another approach to hiding the fields. What you can do is create a new Priority and name this new priority "None", assign it the color white (#ffffff) and for the image url, use a transparent gif (example: http://twinpine.com/wp-content/uploads/2012/06/transparent_gif.gif)."
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs