Yes, your workflow is currently broken. Generally you have to set resulotion when transition an issue to "done" This is usually done in 1 of 2 ways. 1: A transition screen in the last transition that allows the user to set the field. 2: A post function that sets the resolution to a static valule. I want to prevent our staffs from logging work when the ticket is in 'Resolved' or 'Closed' status. I already set up property in 'Resolved' and 'Closed' status of jira.permission.work.denied = denied and then i publish it. Now, when a ticket is in 'Closed' i can no longer log hour, however, i can still log work when issue is in 'Resolved'. Thanks Walter but created vs resolved doesnt work for me because we look at closed status as part of the chart. The issues dont stop at resolved, so want to know how many were closed and how many were created in the same chart that would give me the percentage/count comparison on how many are getting created and how many are getting closed on a weekly basis. 課題の状態は、大きく4つに分けることができます。. 「未対応」：作業に未着手の状態. 「処理中」：作業に着手している状態. 「処理済み」：作業の成果物をチームリーダーやプロジェクトマネージャーに確認してもらう状態. 「完了」：成果物のチェック Resolution status in Test issue different between imported and mannually created test. So my company is recently using Jira and Xray. We have a workflow defined for all issues, including for Test issues. In this workflow we have a status that has a resolution of DONE associated. While going through the list of tests in a project, we noticed Add, edit, and delete a resolution. Select > Issues. Under ISSUE ATTRIBUTES, select Resolutions . Fill in the form below the existing resolutions. You can edit the name and description at any time. Click Add . Don't name resolutions "Unresolved" or "None". Jira automatically shows issues as "Unresolved" when they have no set resolution. you could then add to your JQL. and type = IssueType. So you could have a filter set up for each issue type you wanted to report on - eg. resolved >= startOfMonth (-1) AND resolved <= endOfMonth (-1) AND type = Task. would return all tasks that were resolved in December 2020. As soon as Feb 1 comes along, that would report all tasks resolved in One idea I have in mind: Limit the status to Open, In Progress, Done, Closed and handle the deployment/release over JIRA build-in versioning. If a problem occures on production, a bug ticket must be opened. Otherwise I don't see a chance since the versioning/releasing of JIRA 6.4 does not seem to include status columns by itself. .

jira difference between resolved and closed