John Funk Community Champion

Hi Calvin, Just to clarify, Conditions will hide the transition. Validators will still show the transition, but will fail with an error message if the Validator is not meet. Having said that, can you share a screenshot of the Condition you have created? 

Hi Morgan, It might be a bug that's been introduced. You should probably create a support request to get Atlassian's feedback. https://support.atlassian.com/contact/#/

Hi Sathish - Welcome to the Atlassian Community! I don't think there is an existing template for this, but it should be easy enough to set up. I would create an Epic for each Stage. Then you can link Tasks (or even Epics) to each other so that you can eventually create automation rules to handle the dates. 

Hi Frank - Welcome to the Atlassian Community! Has it been a while since you logged in there? Do you have Jira set up under that domain also? https://kennuo1989.atlassian.net

Hi @stephan_lewis - can you post your final rule, especially showing the details of the lookup tables? That will help future readers of the post. 

Can you list the exact steps you are doing?

So what is the error/problem you are having?

Do you have a specific example?

Did you follow the steps in the article? 

Hi Maciej- Welcome to the Atlassian Community! You should be able to follow this guidance to downgrade the plan. You will need to be an Org Admin to do that. https://community.atlassian.com/t5/Jira-Software-articles/How-to-Downgrade-Jira-Software-from-Standard-to-Free/ba-p/2299949

Very nice - glad you got this going. Yeah, you just need to change out the name of the field or use the customfield ID as you have. 

Great!

Great! Glad to hear. 

You should open a support ticket with them to get their feedback. https://support.atlassian.com/contact/#/

Hi Daniel, Thanks for some of the comparisons! Have you opened a support ticket with Atlassian to request that feature? Would love to upvote that if there is a JAC ticket. https://support.atlassian.com/contact/#/

Hi Darryn, Have you tried different browsers or monitors? 

Great! Glad to hear that worked. To see the account ID, go to Settings > User Management Select a user. In the URL it is a long string of characters. Something like: users/60d2431fdeecef006af21c1e it's the part after users/

Hi Candice - Welcome to the Atlassian Community! You can open a support ticket at https://support.atlassian.com/contact#

Hi Mark, Try using either the email address of the user (the one used by Jira) or the Account ID of the user.

Hi Diane, Go to Project Settings > Features and toggle off the Enable Sprints setting. https://support.atlassian.com/jira-software-cloud/docs/enable-agile-features-in-team-managed-projects/

Hi Michael, That's correct - the rule won't fire until the changes are reviewed and implemented. 

Hi Vera, I would use a custom date field that gets populated with a post function (or same automation rule if that's what is being used to send the email) when the issue is moved into that status and the email is sent. You can use an automation rule based on a Scheduled Trigger that runs daily (maybe at 4 am or something).…

You can try it with just a single issue that you know is within the character limit and see if it barfs on it. Just use key=ABC-123 for the JQL in the scheduled trigger - of course with your issue key. 

Hi Rehma - Welcome to the Atlassian Community! In addition to the other suggestions, the Revyz Data Manager for Jira app in the Atlassian Marketplace does a great job of this. 

Hi Anne, You can create a custom field of URL type to story the link. And then make that field required.

Yeah, sounds like there is definitely something else going on. 

Hi Rudie, Try using the email address of the user in Jira. 

Hi Louis, I just use a bookmark in my browser. That's the easiest way since there is no "default" board. BTW, boards are listed in alphabetical order, so an enterprising user would name their board accordingly to have it show first. :-)

Did you actually try that @Sreenivasaraju P ? Because I don't think that field can be empty -Unresolved is not empty. 

Hi Jenny - Welcome to the Atlassian Community! There might be a bug there. However, I used WAS NOT Unresolved and it gave me issues with the value of Unresolved. You might actually use Status instead of Resolution and WAS NOT IN. Like this: Status WAS NOT IN (Done, Canceled, Completed) Whatever the Done category statuses…