Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,560,577
Community Members
 
Community Events
185
Community Groups

A New CUSTOM field in Issue that need to update status of the ticket

Edited
Abdullah Sa_D Muhammad Answar Vencapah
Abdullah Sa_D Muhammad Answar Vencapah May 24, 2022

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?

Answer
Watch
Like Be the first to like this
499 views

1 answer

0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
May 24, 2022 • edited

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)

Reply

Suggest an answer

Log in or Sign up to answer
Feedback Forum
Announcements
TAGS
AUG Leaders

Atlassian Community Events

See all events