You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello! I would like to know how I can declare a state of my flowchart as closed, since I saw that there were two types of "in progress" state, "In progress" and "ready". But in my statuses that are with the "ready" type, they are not closed, from what I read, the "ready" status is a "ready to close" but it is not the "closed" status, I would like to know then, how do I configure a status, to be able to close a ticket.
Welcome to the community. Statuses in the JSM system is associated with WF setup/design.
In general, all statuses are grouped into one of the three status categories (TO DO, IN PROGRESS, DONE). Each category is associated to one specific pre-defined color (dark gray for TO DO, blue for IN PROGRESS, and green for DONE).
With that in mind, when you define your custom WF status, you need to decide which status category to be used. You can still use a status (that is associated to the TO DO or IN PROGRESS category) to be used as a terminal status of your issue. Although it is not recommended or following the proper standard/best practices.
You already know that you can name your status anything that you wanted, if the status is setup in your WF to be the final status, then it is the "Closed" status for your issue. Therefore, it is up to you on how you wanted to design your WF. JSM is flexible to be customized to fit your needs.
Here are a few guidelines for WF and status design -
1) Statuses are properly assigned to the right category)
2) Terminal status (the last status of your WF) is typically represents the final status of your issue (i.e. CLOSED)
3) In the transition of the terminal status, you need to ensure that "Resolution" field is set. On the other hand, if your WF allows an issue to be re-opened (moving from the terminal status to another valid status), you will also need to remember to remove the "Resolution" field value via the WF transition. This is done by adding the appropriate post-function call.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Great you found the problem with your WF status. if your WF status (one that is in question) is not used by other projects or all other projects are OK for the status to not to be the terminal status in their usage, then you can just edit your status by associating it to the IN PROGRESS category (blue) to clarify how this status is defined to be.
Hope this helps.
Are you stating that those issues are still editable? Using the out of the box WF and status, when an issue is at the terminal status, edit is restricted.
Are your WF status something that you created new? In addition, are those issues' resolution field is not populated?
It seems that when issue moves into the status in question that your WF's transition is not populating the "Resolution" field. You will need to update your WF setup and publish the change.
Afterward, for all existing issues, you will need to move those issue's status to another "In Progress" category status and then move them back to the status in question.