Hide Jira defult fields from issue page

[krasalexander]

I have custom issue type and create screen scehe with two screens:

• screen for create issue;
• screen for edit and view issue.

But all default Jira params are still diplayed on issue page... such as: Priority, Resolution, Affects Version/s and etc.

They are absent on my issue view screen, but it doesn't influence them in my case. How can I hide them?

Thanks for help!

[Chaithra N]

hi,

In the Field Config Scheme hide the required fields.

Refer - https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour for more details.

[MattS]

Be warned that hiding Priority can break the default queries for each project. And hiding Fix Versions will break the roadmap/release notes functionality

[Veve]

What I'm trying to remove is the "Affects version/s" field, which shouldn't break anything. I actually want to keep it in bugs, but nowhere else.

I only have one Field configuration, and in that the field is listed only for "bug" screens. The other issue types do hav other screen configurations. And the field still shows up everywhere.

[Nic Brough -Adaptavist-]

You need two field configurations - the one you currently have, which shows it, and a second one that hides affects version/s

Then you need one field configuration scheme which tells the project to use the one with the "show" for bugs, and the "hide" scheme for all the other issue types.

[Veve]

Wow, that did it! Thanks a lot.

[Alex Perez]

Hi krasalexander,

Fields are shown in this screen if they are included in the "view screen"or are defined visible.

The Field Configuration Scheme used in your project defines which fields are shown or hidden, and which ones are optional or required.

Clone the Field configuration Scheme used in your project in order to not affect other projects, and edit it to hide all the fields you don't want to see in the view screen nor issue browser.

HTH

[zulki yusoff]

I tried this, and it works;

<script language="JavaScript">

function hideUnwantedField()

{

var isIssuePage = AJS.$('#issue-content');

if (isIssuePage.length != 0)

{

AJS.$(".name:contains('Labels:')").parent().hide();

AJS.$(".name:contains('Resolution:')").parent().hide();

AJS.$(".name:contains('Priority:')").parent().hide();

AJS.$(".name:contains('Type:')").parent().hide();

}

}

[Nic Brough -Adaptavist-]

As a general rule, you should avoid using javascript, and try to do it in Jira config. This question can certainly be done in the config.

Javascript has to be retested on every single upgrade and often rewritten, and if you use it a lot, you quickly find it starts to fail as one use starts to interfere with others.

[sharvan singh]

where to write java script code in jira? can you explain it?

[zulki yusoff]

Sharvan singh - you can copy paste above script into the banner section. However just like Nic said it is not advisable to use alot of custom scripting as the upgrade may cause problem in compatibility.

[Kota Sreenivasa Shravana Kumar]

The above java script is not working for JIRA 7.2.1. After setting the above script in banner, JIRA goes blank.

Can any one advise or share, How to hide the system fields ( for example : Resolved ) using JIRA configuration or customization. or provide the compatible script if any available to set via banner.

Thanks !

[Nic Brough -Adaptavist-]

As suggested before - javascript is the worst possible way to do this, and you've walked straight into one of the reasons why.

You should hide the fields with field configurations if you're not using them.  Resolution is a field that you always use though.  Always.  Whether you want to or not.

[Kota Sreenivasa Shravana Kumar]

Thanks NIc for quick response. I agree that javascript may not be the right approach.

Can you let me know, How this can be achieved using JIRA configuration ? Hiding the custom field is pretty straight forward.

I am interested in hiding the system fields using JIRA configuration. Thanks

[Nic Brough -Adaptavist-]

Please re-read the second paragraph of my previous comment.

[John O'Brien]

Gentlemen please,

Why does noboday just say it out straight: it is NOT POSSIBLE to hide certain fields such as "status" and "resolution" using the standard configuration methods of JIRA i.e. Field Configuration Schemes or Screens. The displaying of these fields cannot be influenced by the project or JIRA administrator.

[Nic Brough -Adaptavist-]

The original answer, in 2013, did.  It seems to have gone.

[Carmen Bullock]

Thank you John. I was looking for the same answer. I can't find a way to remove the priority field off of the parent screen or case.

[RS]

To add or remove fields from your custom screens go to:

From the Administration screen, click on "Issues" > "Screens"

Locate your custom screen and click "Configure"

From there you can add, remove, and redorder the fields for that screen.

-rick

[krasalexander]

I have tried it, - these fields (priority, affected and etc.) are absent on the screen, which is cofnigured for issue view.

[John O'Brien]

KrasAlaexander,

nobody seems to be reading your question properly.

I wanted to do this also when I started using JIRA. Like me, you have not included these fields on any of your screens, yet they are showing up when viewing an issue. That is because these fields are displayed separately by JIRA or independently of how you configure your project. You can define screens, screen schemes and field configuraitons etc. all you like. Unfortunately these have no influence on certain standard fields such as Resoluiton and Status. Sorry, but you cannot hide these fields using the normal methods.

[Veve]

John, thanks a lot, your answer is the one I was looking for (even though I'm not sure if krasalexander is still looking for it).

[Nadir MEZIANI]

Hi,

This link can help you to know more for Configuring Fields and Screens

https://confluence.atlassian.com/display/JIRA043/Configuring+Fields+and+Screens