Block Out Conditional Field Resolution For Free

Step 1: Determine the Deployment Type There are three Jira deployment types: Cloud, Server, and Data Center. The different types have different features and capabilities. If you have Cloud, Atlassian hosts the application on their servers and they are responsible for upgrades, email, and up-time.

Status categories: Jira lets you collect many statuses under a to-do, in-progress, or done category. These categories help you sort, filter, and report on your project work. For example, you might have a ?Backlog? to-do status and a ?Waiting for approval? to-do status.

Resolution in JIRA In order to do this, you will firstly have to obtain the resolution ID that you want to exclude. Here's how: Go to the Resolution tab under Issues section > Issue Attributes section. You should see all the resolution options.

Solution Go to the project settings > Workflow; Edit the desired workflow; Find the transition that will reopen the issue and click on it; Navigate to the pop-up and click on Post Functions, then click Add post Function; Add the Clear Field Value event as a post function; Select the Resolution field and click add;

Resolutions: Any issue that has the Resolution field set is treated by JIRA as "resolved". A JIRA issue can be resolved in a number of ways. The default resolution statuses are: Fixed, Duplicate, Won't Fix, Incomplete, and Cannot Reproduce.

Closed means that the issue has been worked on but can be reopen. Resolved means that the issue has been worked on, closed and a resolution determined. An issue is Open if its Resolution field has not been set.

The Resolution Time report for Jira Cloud displays the time spent per issue in unresolved and resolved statuses. For example, you can see the totals for all the combined resolved statuses for a particular issue, including number of times updated and average time.