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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi All,
Can you please advise me about an new custom field.the custom field name would be Status for example the field has two possibilities open and closed it depend when the agents closed or opened the field need to updated?
Welcome to the Atlassian Community!
You should never be updating status based on a custom field. Status changes because the issue moves through the workflow, which is something your humans or automations should be doing at the right time. And you should never have more than one status field, the status is an indicator of where an issue is in its lifecycle, and hence should be unique (otherwise you end up with issues that are in quantum superpositions, or with status that is totally inconsistent depending on who is looking, which is the antithesis of what an issue tracker is for)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.