John Funk Community Champion

Hi Jovanio, Being a site admin really has nothing to do with it. But you should be able to see filters that you created at least. Where are you looking for the filters? 

Hi Joanna, Nothing really that I know of outside of trying other apps. But you might could send an email to them if they create an entry without that field being populated. Maybe by Automation for Jira or ScriptRunner if you have one of those. Then if you keep having problems with the same team member who won't fill it…

Thank you for sharing. What will you do with that key now? Can you not just add an action after the Edit Issue? 

Okay that seems to be pretty unique. I would submit a support ticket to Atlassian to see what they say. Might just be a bug with that particular method. Please post the resolution back here for future readers of this post. Good luck! https://support.atlassian.com/contact/#/

Hi Muhammad, It is always best to post a copy of your rule which asking a question like this. Please do that and let us know exactly what you want to see at what step. 

Hi Jane - Welcome to the Atlassian Community! It sounds like you are going from a Team-managed project to another Team-managed project. Which technically those are different fields even though that have the same name because they are independent projects. Jira just looks at the name in this case during the move. 

Hi @박성민(학해) This is probably because it is picking up multiple statuses from your Team-managed projects because technically those are different statuses within Jira. If you try just using a single project rule, that might cut down on the values shown. 

Hi Noora - Welcome to the Atlassian Community! Technically you couldn't have 251 Active Users, therefore the last person would not be able to log on. 

Probably so @Barbara Szczesniak - but feel free to add other weird habits that you have. I GUARANTEE @Kristján Geir Mathiesen has more weird stuff he could share. :-) Maybe this could be a lightning talk for him at the Community area during Team 24!

Hi Hein - Welcome to the Atlassian Community! It's not currently possible to do that in JWM. I would suggest you vote for and follow this open Atlassian feature ticket: https://jira.atlassian.com/browse/JWMCLOUD-111 Also, if you have a Premium Subscription for Jira, then you can probably do what you want to do using Plans. 

We probably all have a few friends like Robita and Luigi haha. Thanks for sharing - I would love to know what you call the next plant you get. Especially in light of knowing it's soon demise (ala Robita and Luigi). 

Awesome! Sounds like a perfect name. 

Sounds like a future Quiz Master question to me!

Hi Kelly - Welcome to the Atlassian Community! How are you defining "Scheduled issues"? Can you share a screenshot? 

Hi Alfredo, This sounds like a bug. Have you tried with other browsers? What type of project is it? Company-managed? Team-managed? Software? Business? 

Hi Rakibuzzman - Welcome to the Atlassian Community! What type of project is this? Business/JWM? Company-managed? Team-managed? Can you share some screenshots of what you see? 

Hi Dave, You will need to use = and not <= to have it only send one time. Otherwise it will keep sending everyday once it hits that date. 

Hi Sadhana, Have you thought about doing that with an Automation Rule? 

Yes, you can provide a default value for the Acceptance Criteria field.

Hi Danieele, These are often just defaults based on a template you may have chosen when creating the project. If those don't really mean anything to you, you can sub them out in the workflow for statuses that have better meaning. But I would say that when an issue is created it goes into New - because well, it's new. Think…

Hi Baiju - Welcome to the Atlassian Community! Can you share some screenshots? Please include the overall workflow as well as the individual status with the approval details shown. Also, are you using the Approvers field for the approvals? 

Hi @sheldon.gonsalves - Did you ever get this solved? Interested in the answer. 

Hi Takanori - Welcome to the Atlassian Community! See if this helps you. You will need to translate it. https://support.atlassian.com/confluence-cloud/docs/getting-started-with-confluence-whiteboards/

Hi Osama, If you want it to be mandatory at issue creation, then just make the Assignee field Required in the Field Configuration for the project. If you want it to be mandatory later on in the project, then add a Validator in the workflow for the transition to the status that you want to force them to populate the field.…

Right there is a bug in the system that won't allow you to drag those up and down. And you can't Add the initiative type at level 1 while also deleting Epic. What I have done in the past is to delete the Epic issue type first, but this was on a brand new instance. Then add the initiative to level 1, and then add Epic back…

Hi @Saki Okubo - Welcome to the Atlassian Community! The short answer is no, you won't be able to do that. The next question is which setting are you changing that you want this for? 

Hi Krish, Boards are just views of the data, so they have no impact on being able to trigger things or prevent them. Fields are attached to Projects and/or Issue Types. So unless the boards use different Issue Types, then you will not be able to do that. If they do use different issues types, then create a Field…

Hi Kelvin, Try {{parent.issue.custom_10157}}

Hi Tarun, First, yes it is now called Timeline and not Advanced Roadmap anymore. Same object, just different name. Can you share some screenshots of your Hierarchy and the Epic screen with the Parent field? Are any issues showing in the Parent field? Are you typing the value of the key for the Initiative?

Hi Martin, You won't be able to create a dynamic automation like that. You could create a separate rule that would be manually executed by the Agent.