![]() ![]() Select the relevant "Field Value", then click Add.Select Update issue field, then click add.On your right corner, click Add post function.Select the transition to the "Done" status.Find the relevant workflow, then, on your right corner, click the pencil icon to edit it.Open your project > Click project settings > Click workflows on your left sidebar.(for instructions purposes, let's assume the last status of the relevant workflow is DONE) Create a post function on the transition that leads to the "Done" status to set the resolution as something fixed: The setting of the resolution field can be achieved mainly by 2 ways: Solution The following instructions are meant to prevent current issues from having the resolution field mistakingly set. If your team finds results for any of these queries, please consider implementing the solution below. This would mean that the resolution of your issues is correctly set on your Jira's Cloud instance. The ideal scenario is for both queries to yield no results. These are strong evidences that the "Resolution" field might not be configured according to the best practices on your Jira's Cloud instance.Īs a Jira admin, there are a couple of JQL queries that you can perform to verify whether the "Resolution" field of your instance is configured according to the best practices or not. "Open Issues" are retrieving issues that are in a DONE status category."Created vs resolved" reports won't yield the expected results.An issue in an "In progress" column of your board being already strikethrough'ed.Such scenarios can be (and they are not restricted to): There will be situations where your team might notice odd behaviours when navigating through and working with Jira. Keeping the "Resolution" field working according to the best practices is crucial for your team to leverage Jira on exploring your company's potential. System filters (for example, "Open Issues").Reports about issues (for example, "Created vs resolved").Issues having its key strikethrough on boards.Some of them are (and they are not restricted to): There are many native functionalities in Jira that depend on the "Resolution" field. This will lead to confusion and is strongly not recommended. So adding a resolution named Unresolved/None and setting it in an issue will mean that the issue is seen as resolved. The Issue Navigator displays "Unresolved" when no resolution is set for an issue. Don't create a Resolution named "Unresolved"/"None"Īny issue that has the Resolution field set is treated by Jira applications as "resolved". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |