I am currently facing an issue with the "Resolution" field, which does not appear in the "Issue view". I give you more details below.
I have configured a specific screen for a specific issue type that I called "Support request". It gathers two tabs with different fields, as shown below:
You can see that I have put the "Resolution" field in the second tab.
When I create a ticket "Support request", this field does appear:
However, once the ticket is created and that I want to check it from my board or my backlog, this field is not displayed anymore (in neither of the tabs):
I have checked the issue layout of this ticket, and it does appear:
To be noted that I tried something else just in case: I changed the issue screen of this issue type by putting the "Resolution" field in the first tab instead. In this case, the "Resolution" field would not appear at all in the issue layout configuration panel.
Could someone tell me how I should do to display this "Resolution" field in the "Issue view" please ?
Many thanks :)
For 20 years now, Jira has had a simple "is this done" flag.
If the resolution field is empty, the issue needs attention. If it has a value, then the issue is resolved and needs no more attention.
It's an absolutely binary thing - empty or filled.
If you put the resolution field on an issue update screen (create, edit or transition), then the human using it will either have to select a value, or accept the default value.
No matter what their choice, they will set a value. The field, while not "mandatory", will not let you leave it blank.
If you put the resolution field on the create or edit screen, your people will be closing the issue when they create or edit it. Which is, in 99.9% of cases, wrong.
Do not ever put the resolution field on a screen. (Other than a screen you are using for a closing transition and nowhere else)
I found that the field appears when once the ticket is put to "Done".
It means that I cannot setup a rule related to this field as I wanted: "The user cannot put the ticket to "Done" if the resolution field is empty.
Anyway, at least the field appears, thank you all!
To explain this a little - Jira hides some fields in some displays when they are empty - it won't show the field name or the (lack of) content at all.
Your "rule" is actually done the other way around in Jira - that's actually "using Jira as it was intended". You don't do "can't put issue to done if the resolution is empty", you do "set the resolution as the user moves the issue to done".
The usual way to do that is in the original workflow Mike and Scott built for Jira 1, and is the reason the resolution field works this way. When moving an issue to one of the two "done" status in the workflow, there is a transition screen that has the resolution field on it. (And for "reopen", there's a post-function that clears it)
Hi @Axelle and welcome to the community,
Resolution field, but also other fields as well placed inside a screen, are visible when populated. However, resolution is a systemic field which you can't simply edit. Consider it as a very special field. Resolution appears next to the status, when and if populated:
First many thanks for this warm welcome !
To answer you comments:
Hi @Axelle ,
Welcome to the community !!
To a field to be available in screen after ticket is created, it should be added in View screen and If you want it to be editable, then the Resolution field should be added in Edit screen of the ticket type.
Go to project settings --> Issues --> Screen
Check what screens are associated for Create/View/Edit actions.
Please note: If the Resolution field is present in all three screens, it will only be displayed in the issue when some values is added to the field.
@Axelle - no, you have not misunderstood the purpose of the field. It is there to record a headline of why you are saying "this issue is done with".
@Rilwan Ahmed - yes, resolution is a critically important field in Jira and you never never never want to set it at the wrong time. Such as during an edit action. Never add the resolution to an edit screen (as part of daily operations. It is ok when you're trying to fix the mess made by another admin adding it to an edit screen when they shouldn't have, but that is very much an edge case)