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; } } }

How to restore deleted default fields and auto-generation of 'Unresolved' status in Jira

김진우_ogaoyz

I deleted the default fields provided on the "Solutions" page.

As a result, the "Unresolved" status that used to be automatically generated when creating an issue is no longer being automatically created.

I'd like to restore it, but how should I proceed?

"How to restore deleted default fields and auto-generation of 'Unresolved' status in Jira"

Accepted answers

Joe Pitt

As far as the resolution, it isn't auto-generated, it starts that way. The unresolved in the resolution field means the cell in the database is NULL. If you had a value of 'unresolved' in the resolution select list you need to get rid of it.

All comments

Nikola Perisic

Welcome @김진우

Statuses are part of the workflow and it is not connected with the fields. Screens are used to define which fields will be appearing when the issue has been created, viewed or edited.

To restore the status of the workflow, you either need to have the Edit Workflow permission, furthermore to be the Jira administrator.

Could you explain what do you mean exactly by restoring default fields? Restoring the issues in Jira is not possible, unless you are using a third party application.

Marc -Devoteam-

HI @김진우

Welcome to the community.

So you deleted all the options from the "Resolutions", did you add new ones, or did you just remove all?

Can you show the current config in screenshots?

Joe Pitt

김진우_ogaoyz

First of all, I'm an administrator, and in the initial setup, 'Unresolved' was automatically generated in the 'Resolution' field every time an issue was created.

I deleted all options, but there was one 'Resolution' that couldn't be deleted, so I deleted everything except that and then recreated it.

For now, I have resolved this issue through automation.

I apologize and thank those who have replied.

스크린샷 2024-11-01 203118.png 스크린샷 2024-11-01 203325asdasdasd.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud