The Permissions 'Resolve issues' and 'Close issues' are generally used in the workflow as transition conditions. They are like of shortcuts used instead of mentioning the roles/users who should be able to see the transitions. If not used there, these 2 permissions do not work on it's own. It is meaningless. Dashboard - tickets closed by month. Community. Products. Jira Software. Questions. Dashboard - tickets closed by month. wait until no-one else is going to be using the project (s) affected. go into the project (s) and add the resolution field to the "edit" screen they are using. run a search for something like "status = closed and resolution is empty". Bulk edit them, setting the resolution. Step 1: Add these five gadgets. Start with the bare necessities. We'll put the team's overall workload, incoming tasks, work split by team member and due date, and high-risk issues front and center on your JIRA dashboard. Add: Filter Results (add this one twice) Created vs Resolved Chart. Assigned to me. 1 accepted. Created simply reflects issues created, e.g. project = abc will show all issues created for the ABC project. Resolved is defined by setting the Resolution field, e.g. project = abc and resolution is not empty will yield all issues in project ABC that has been closed w/ a Resolution set. Hi Jack, thanks for your response. Automation rule – Auto-close after being resolved for 3 business days. Your IT service project includes an automation rule that auto-closes requests after they have been resolved for three business days. This rule transitions a service request from Resolved to Closed when the above SLA is breached. You can disable or edit this rule by I added this in case some of you have created and closed tickets in an administrative way after the fact. While not ideal, it is sometimes the case. In this situation **JIRA has a bug** If you manually set the closed date the filter will still use the ACTUAL date you resolved the ticket. EXAMPLE: Looking at the ticket in JIRA WEB Well there are two ways to achieve this. but both have to be implemented by an admin. First add a screen with the Resolution field to that transition. Then a user has to choose a Resolution during that transition. Or second. the Resolution is set via postfunction during that transition. Like. rTfdG.