nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira 6.2-Hide/remove resolution for a single project

Sred

Good afternoon,

I am trying to come up with a way of hiding or removing the Resolution field from appearing in JIRA when viewing a JIRA Issue. We have built a custom workflow with custom fields, so we do not use the "Resolution" field for anything (in this specific project). everything I have been reading is that this is not able to be accomplished, although for different versions of JIRA (5.2 etc). Is there a way in 6.2 to remove/hide this field? I have already removed "Resolution" from the screen configuration, but it still appears.

Thank you.

Accepted answers

Nic Brough -Adaptavist-

Have you tried hiding it in the field configuration?

>we do not use the "Resolution" field for anything

Ah, that's going to break the standard reporting. If you don't use the resolution field, JIRA doesn't know when an issue is done. Even if you hide it, you need to set it.

All comments

Nic Brough -Adaptavist-

Have you tried hiding it in the field configuration?

>we do not use the "Resolution" field for anything

Ah, that's going to break the standard reporting. If you don't use the resolution field, JIRA doesn't know when an issue is done. Even if you hide it, you need to set it.

Sred

Wouldn't hiding it in the field configuration affect all of our other projects that do rely on the resolution field? I saw that as a viable option until I read someone state that this caused multiple issues on other projects that relied on this field.

We have a custom field that we track for the status, so the "Resolution" field is always in an Unresolved state (custom filters for reporting).

Nic Brough -Adaptavist-

No. You can have different field configurations for different projects, and even issue types within projects.

>We have a custom field that we track for the status, so the "Resolution" field is always in an Unresolved state

That's really not a good way to handle it. Use the resolution properly (At least until Atlassian deal with the issue that it's a bit of a rubbish way to do it)

Sred

Ahh I see now, field configurations for default fields in Jira, are handled on a Project by Project scheme. Thank you, that resolved my issue completely.

I agree that we should have used the resolution field, but that choice was not mine to make.

Thank you for the help! It is greatly appreciated.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration