John Funk Community Champion

Regardless of Atlassian's intent - they are just names. You should not implement processes that you don't understand or know what they mean. You should implement YOUR processes, not someone else's. 

@lila @Bill Sheboy Was there ever any resolution for this?

@Jeffrey Bistrong - Did you get this working?

Hola Luis, Lo siento, pero no estoy siguiendo muy bien el escenario. ¿Puedes escribirlo paso a paso?

That looks like a combination of custom fields and statuses. You should have clear process that you want to achieve, and identify the fields you need populated to relay information. 

こんにちは @musa - Atlassian コミュニティへようこそ! Jira の無料バージョンでは、ユーザーと権限を制御できません。これを実行するには、有料バージョンにアップグレードする必要があります。

Jira would consider those to be two different users. 

Take a look at this and see if it helps you. https://jira.atlassian.com/browse/ID-7692

Hi Suparna - Welcome to the Atlassian Community! You should contact the vendor directly for support. 

Very good sources there!

Like @Dave Mathijs - I was always nervous every year starting school. I knew I would know most if not all of the kids who would be in my class at my school, but was anxious nonetheless. I was very shy back in those days but would get settled in for the most part after about a month into classes. 

Hi @Nurseflow - Welcome to the Atlassian Community! You need to open a support ticket with Atlassian and have them check to see if the email address is on their suppression list. https://support.atlassian.com/contact/#/

Hi Harold, If this is a new instance you can you rename the Epic to Feature. Then create a new Issue Type and call it Epic. Then you can add that new Issue Type above the Feature. But renaming will affect all of your current Epics - which you might want anyway. 

Thanks @Janice !!

Hi Sunny - Welcome to the Atlassian Community! You should be able to use a condition to check for the initiator being the Automation for Jira user. 

Hi Haneena, You would need to delete those extra boards. Click on the Your Work menu option in the top nav bar and select Boards, then View all boards.

Hi Aasim - Welcome to the Atlassian Community! Is this a user that was active before? You might check in the User Directory: Settings > User Management > Directory -> Managed accounts -> reactivate account.

@Vronik - I don't believe the incident has anything to do with inviting users. 

Yay! Glad it is working for you. 

Ah, it looks like there is an automation rule that is creating the issue in the first place. So, maybe this rule is not even firing because the rule needs to have a box checked on the Rule details page to allow another rule to cause it to fire. 

Can you please share the audit log? 

Hi Liana, Jira Server version is no longer supported, included for new downloads/installs. 

Hi Drishti, Can you include the audit log for when the rule runs? And what is not working? What is not happing that you expect that it should? 

Hi Rahul, One way is to look at what rules are getting executed the most and see if there is an alternative to the way the rule is set up/running. Go to Settings > System > Global Automation Click on the Usage tab and scroll down to the bottom. One suggestion is to use scheduled triggers and run a few times a day instead…

Hi Ylan, Yes, it should. You might want to create a test space/page through and run it through and see if that works. 

Hi Christina, I have not seen that error before. Have you removed the link in the trigger issue? The delete should have done that, but something might have dropped. And you are sure that issue has been deleted? Can you see other issues on that same TAMPIT project?

Thank you!

Well done!!

Understood. 

That's good to hear! Not sure when it got fixed, because a few weeks ago it was not triggering.