I presume when you say alert you mean an issue. It should not be on the create or edit screen
Resolution Field
Resolution Field can't be made optional. DO NOT put the field on any screen except the one presented in the transition where it is to be set. Resolution is a special field in JIRA. It has an initial value of ‘Unresolved’, which means the field is NULL in the database. It is ALWAYS required when it appears on the screen. ONLY display it on the screen during a transition to the status where you want it set. Once it is set the issue ID will appear with as strikethrough. If you re-open an issue the transition from closed to reopen needs to have a post function to CLEAR the resolution field to set it back to Unresolved.
Limiting resolution options
You can do it with workflow properties. Use the jira.field.resolution.include property. copy/paste https://confluence.atlassian.com/adminjiracloud/workflow-properties-776636709.html
Yes am talking about issue and it's not for all issue few created issues are not having resolve option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correctly created issue is having resolve issue option while other image is without resolve issue option
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You don't have the permission to use the "resolve issue" transition, or the transition does not exist out of the current status of the first issue.
Check where each issue is in the workflow and what the workflow says for who can use transtions out of the current status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic Brough
I have the permission infact the option is visible in other created issue and m able to resolve those issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you 100% sure that the workflow conditions allow you to resolve the issue from the status it is in in the first screenshot? What do the conditions on the workflow transition you are trying to use say?
After checking the workflow (and I'm repeating it because your reply does not convince me you have, and 99.9% of these type questions, it is that the workflow is blocking it), you might try the integrity checker. If that finds a problem with your issue and its workflow it can correct it, but then you will need to start looking at what caused it to get corrupted (the "create alert" process is probably broken)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Admin -> Integrity checker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.