How to add field shown in issue page?

[Karmandroid Singularity]

How do I select (add / remove) field to be shown in the issue's page.
In this page I wanted to add another field to be shown, something like "Review Result", etc.

[Niranjan · Accepted solution]

Hi @Karmandroid Singularity ,

For the custom field to be visible on the issue in your project

1. The custom field should be added to the view issue screen 
2. The custom field should be associated to your project with the custom field context.
3. The custom field should have value in the issue. You will not be able to see the field on the issue unless you provide a value. You need to add the field to create/edit screen and provide values for the field on the issue.  Fields with no values will not be displayed on issues even if has a field context and project/screen association.

[Karmandroid Singularity]

Hey, @Niranjan 

I just noticed that the fields must have value for it.

But what I want is that those fields are always shown, so the Reviewer will be able to see and fill the fields without going through the "EDIT" button.

I don't think it's possible, no?

[Niranjan]

Hi @Karmandroid Singularity  In that case, you can add a default text value to the field so that it will be visible after issue creation , something like "Review Result". The user may need to edit the value when required.

You can also add a workflow transition, restrict it to concerned stakeholders and make the "Review Results" field mandatory. In this way, you can force the field to be updated via pop-up screen

[Karmandroid Singularity]

Yep, 
But the problem is to do that I need to contact my JIRA Administrator.

SO, this is one side that I hate from JIRA, Project Administrator has very limited access on editing things such as screens, resolution (post function, etc). Because those things are shared for many projects.

I am think a features that allow Project Administrator to manage each of their own projects. Like the possibilities of creating custom scenario, screens, etc, in addition of using the one shared for all projects.