John Funk Community Champion

Hi Lavanya - Welcome to the Atlassian Community! What type of project is it? Team-managed? Company-managed? Are you using a Backlog functionality where the Backlog column is not on the board? Can you share a screenshot of the board and the menu structure to the left? Basically the whole screen. You can blank out or hide…

You cannot use Request Types with the Sub-task Issue Type - period. You need to give up trying to make Sub-tasks work on your portal. 

Hi Martina, Create an automation rule based on Issue Transitioned. Select your Done type status. Add any Conditions if needed for those certain ticket types. Add a Branch for Linked Issues - choose Relates to Add an action under the Branch for Transition Issue. Select the status you want the linked issue to transition to. 

Great!

Sure - you can have multiple security levels that you create based on different needs. So you can apply whichever one is the case. In this situation, create a level based on just the Assignee and Reporter having access. Though I tend add the Jira Admin group as well to all levels for troubleshooting. But you can leave that…

Hi Fiona - Welcome to the Atlassian Community! Was the org admin the only one? Or is there someone else still there who is also an org admin? If no one, you will probably need to open a support ticket with Atlassian to get you (or someone else) added as an Org Admin. https://support.atlassian.com/contact/#/

No, I just got confused when I saw you mentioned behavior. 

Hi Nandini - Welcome to the Atlassian Community! What exactly is the trigger that sends the email? Is it an automation rule? A built in Jira process? What are the steps to reproduce what is happening? And what do you want to happen when? 

Hi @의연 윤 I suggest you implement issue level security: https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html

Hi Marsha - Welcome to the Atlassian Community! Basically, you can follow these steps. * Create a Company-managed Jira Work Management project - this will become your "template" so you can name it as such. Add a project category to the Project Details page which will unique identify projects using this template. * Create…

Hi Sahil, Take a look at this article that will guide you through how to do exactly what i think you want to do. https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

So the problem is with the rule recognizing the value in the field. Put the rule back in please. Then we can test further. How are you populating the value in the field? Are you typing it in and saving it first and then doing the transition? Or are you populating the field with a screen as a part of the transition? 

So, you are using ScriptRunner Behaviours app?

Hi Ivan, No, I am not aware of a way to do that programmatically - only manually. 

Okay, I am confused - is your problem that you can't update the Request Type name? Or is it that you can't transition the issue after you update the Request Type? 

Okay, that looks fine - thanks for sharing. The error says it is a permissions problem. So does the user have permissions to transition issues? Is this the same user that transitioned the issue to its current status? One test is to remove the current rule and then test again to see if you get the same error. 

Hi Consuelo, Are there other rules on the transition? Especially one involving permissions? Can you share of screenshot of the rules? 

Hi Michelle - Welcome to the Atlassian Community! Depending on the type of project you are creating (Company-managed or Team-managed), you set up permissions for each project so they can only be seen by certain people. For Jira Work Management projects, all users will need a license. 

Hi Balaji - Welcome to the Atlassian Community! 1. You can add a new status by editing the workflow attached to the appropriate issue type on a project. Are you using a Team-managed or Company-managed project? 2. You will need to add a transition from the Declined status to the Open status in the workflow. 

Barbecue nachos (or nachos al pastor) are the best! Chips and a great salsa are one of the most perfect appetizers!

I pretty much love all Indian food!! The spice combination is perfect for me. 

I don't know of another option right now. @Sanket Parlikar {Revyz} - Can Revyz do this? 

Hi Makmur - Welcome to the Atlassian Community! This is the id of a user. Is this user still active? Did you try again later? 

Hi @Jar Lady Why are you using links instead of the built-in parent/child relationships? 

Hi Mohammad - This would involve a fairly detailed response based on your actual environment and implementation. Basically, the tool should implement your Agile practices/processes and not determine or drive those practices. Feel free to connect with me on LinkedIn. https://www.linkedin.com/in/john-funk-92261a38

Hi Luis, Not sure what you are asking. Can you provide an example?

Hi Colleen, I have started to see this show up in my instance as well. Not sure what is causing it. Probably best to open a support ticket for Atlassian to comment on. 

Hi @saurabh.1.jain - So sorry! This got buried and I lost track of it. Did you ever get this working? 

Hi Damien, One way to solve is to create a Condition using JQL right after the scheduled trigger. Use the exact same JQL. I know that is redundant, but now the Condition will fail and the rule will stop processing short of the Send email action. 

Great to hear! What was the actual solution?