John Funk Community Champion

Hi Aniket, You can simply add a Field Required Validator to the transitions for transitions 6-10 and select the field you want to be mandatory/required. 

Hi Jean, You need to remove the Org rights first, then you should be able to delete. Here is how to remove the Org rights: https://community.atlassian.com/t5/Jira-articles/How-To-Guide-Removing-a-Jira-Cloud-Site-Admin/ba-p/1732624#M4816

Not sure how old I was - maybe 9 or 10 - but my nephew (2 years younger than me) and I had built a little fort of sorts with cardboard boxes in a back room of my parents business (it was a very large warehouse type of room). And then we had a candle which where were striking matches to try to light because it was dark. My…

Sounds like it might be in a post function then. If there is nothing in the history for a field it means that the value was in the field when the card was created. 

Hi Srujan - Welcome to the Atlassian Community! Make sure you are in the group. Once you add yourself, then it should show up to be able to add it. After you add it in the permission scheme, you can take yourself out of the group if you like. 

Hi Nick, Most likely it is from some type of automation or is getting set with a post function in your workflow. If you look at the history of the issue does it say who is adding the value? 

Hi Barry, Atlassian has rolled out the ability to have multiple people be able to edit dashboards. Would that solve your problem? 

Hi Emanuele - Welcome to the Atlassian Community! If they are licensed users, you can create an automation rule that adds the users as Watchers to the issue when it is created. 

Ah, I have a better understanding now - thanks for the explanation. I can duplicate the same in my instance. I guess one solution might be that you can move multiple cards at once by holding down the CTRL button and selecting each card and them move all of them at one time. Would that help? 

Hi Frederik, That's a great question - I can't find a way to edit it either. You should open a support ticket with Atlassian to see if they have an answer: https://support.atlassian.com/contact/#/ Please post back here with the response. Thanks!

Hi Greg, You should be able to create a rule with an Issue Transitioned trigger that fires when the issue is transitioned to Done. Then update the downtime field with this formula: {{issue.created.diff(now).minutes}}

Hi @Boleslaw Nowak No, there is currently no trigger within automation for when the Rank changes. I think that's a super idea. Maybe Atlassian will add that feature request to their backlog. :-) @Simmo 

Great - thanks!

Hi @Gayathri B It sound like you are wanting to create a roadmap that uses all 5 epics on it? Is that correct? 

Hi Elie - Can you share how it was resolved for others seeing this post in the future? I assume you changed how the Epic Link was getting populated to not use the trigger issue. 

You are not going to be able to hide a field "sometimes". You can either see the field or not. And you can either edit the field or not. 

Okay, I am confused. Is the comment in the description field? Or somewhere else? 

Hi Asim - Welcome to the Atlassian Community! Sounds like your email address may have been blacklisted with Atlassian. Let me see if someone from Atlassian can take a look.

The you want to control who can Create issues on your project. Simply change the Permission Scheme to make it so that only you can create issues. 

Do you see the comment? 

That's the problem, I think. The multiple issues will not transition when there is a transition screen attached. If you removed the transition screen as a test, it would probably work to just move the collapsed parent issue.

Olá Caina - bem-vindo à Comunidade Atlassian! Isso acontecerá se você já tiver 3 pessoas atribuídas ao Jira Service Management (e talvez o Confluence, mas não me lembro do limite para isso). Se você remover um usuário do Jira Service Management, poderá adicionar outro usuário. Em seguida, você pode adicionar o usuário de…

I am confused then, your first line above says 'I'd like to hide the transition "assign"'. So are you saying that you don't want people to be able to update the Assignee field if it is in a particular status? 

Nope, there's not even any add-ons that will work with Cloud. There is server, but not Cloud. 

Hey Alexander, What type of project is this? If I understand you correctly, you want to change statuses of the issue (not really change columns) but have the card stay in the same column? Is that correct? If so, it will really depend on the type of project it is.

Ah, I see. No, you will not be able to limit the items of a pick list field based on the items in another field with Jira Cloud. 

Do you have a transition screen on the transition from Backlog to To Do in your workflow?

Hi @Kirk Douglas - Welcome to the Atlassian Community! You can't have values appear in a field based on the value of another field while in the create process. You can update the second field based on the value of the first field when the issue gets created by applying an Automation rule. Is that what you are going for? 

Great! Glad it is working for you now. 

Hi Elie - Welcome to the Atlassian Community! Can you share some screenshots of what you have so far?