John Funk Community Champion

You probably just need to change the Parent to {{triggerIssue.parent.issue}}

Hi Prajwal, You will need a Premium Subscription for Jira in order to build out a hierarchy above Epic. 

Hello and Welcome, Max! We are glad you are here!!

Hi Forrest - Welcome to the Atlassian Community! no, that’s not possible. There is only a single approval notification that can be sent. if you don’t need the ability to click on the Approval button in the email, You can create a set of automation rules that can send customize notifications with the links that take them to…

Hi Sofia, No, you cannot add custom fields into the standard notification template that gets sent. There’s an open request for that, but you would need to create an automation rule to send a separate email if you want to have custom fields

Hi EG, No, you would need to control that with either JQL condition or other condition leading into that

Just go to Settings > System > Global Automation. That should give you a list of rules for the entire instance. Then just scroll down the page looking for any rules that have more than one project listed for it under the Projects column heading. You probably have multiple pages, you will have to go through every page…

Hi Vladimir, You can not have a sub-task as a parent of another sub-task. Sub-tasks can only be children. So you need to replace the issue key for the parent. When it is processing, it is picking up Sub-task as a part of the JQL attached to the Scheduled trigger, then you are showing the current issue as the parent. You…

Hi @Lisa K - Welcome to the Atlassian Community! In what aspect did you add a custom field to the Notification Scheme? Was it just an Add? Also, did you use the Permission Helper to see why a message was not received? 

Hi Melissa, The limit also applies to rules used by multiple projects in the rule. So you can't just click on the Global rules menu option to determine that. You need to go through the full list of your rules to see how many use multiple projects. 

Great! Glad I could help. 

This doesn't seem right. You should probably open a support ticket with Atlassian to find out what is going on. Please post back here with the resolution. https://support.atlassian.com/contact/#/

I would still contact ScriptRunner (Adaptavist) vendor. 

Great! Glad I was able to help. 

Check your Notification Scheme for that project to see when the Request Participants are receiving notifications. It probably won't be that field per se, so they would need to be added to a project role. 

You should be able to see those on the List view. The other option for now would be to create a second board for the project which is based more on a Jira Software board with all of it's functionality. But it would still just be for issues on your JWM project. Here is an article that will help you with creating the second…

Hi, Personally, I would not create statuses like that- they are a distortion of Agile practices among other things. Take a look at this article and see if it would help you accomplish what you are trying to do: https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

Hi Reagan - Welcome to the Atlassian Community! They are not getting deleted, they are just disappearing from the board by design. And that can't currently be changed. There are some open feature requests out there that you should vote for and follow: https://jira.atlassian.com/browse/JWMCLOUD-116…

Hi Kelly, No there is not that level of granularity with Notifications. You could submit a feature request for that though. 

Hi Nikhil - Welcome to the Atlassian Community! I don't have the server version of the Automation for Jira app - but have you built a rule and tried it? Just try putting the Request Participants field in the TO: portion of the Send Email action. 

Hi @Sune Fonternel - Did you ever get this working?

Hello Omar! Thanks for joining us here!

Sure - but you will probably need to be a Jira Admin to do that, but you can try it as a Project Admin. Go to Project Settings > Summary then click on the Screen Scheme for the project. Once on the next screen, see if there is a separate Edit screen from the View or Default screen. Click on that and then see if the Due…

Hi Dan, You can use this in the body of the email for a clickable link to the issue. <a href="{{issue.toUrl}}">{{issue.summary}}</a>

Hi Nathan, Here's an article that I wrote about creating a second Agile board, but it would apply for creating a JSM board as well. https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

Hi Julien These suggestions all appear to be aimed at the ScriptRunner app. Do you have that app for the Cloud? And if so, but you cannot figure out where the script is, then contact the ScriptRunner vendor for assistance. 

Hey Alex, When you are using the new issue view screen now, it kind of combines the view and edit screen into one. This means that you are automatically in Edit mode when you enter the screen for fields that exist on the Edit screen. If the field is not on the Edit screen but is on the View screen, then you can see the…

Is that your view? Or the Org Admin's view? 

Hey @Tom Vernier - I know this is really old, but unfortunately, no, this wording cannot be changed. 

Hi Katie - Welcome to the Atlassian Community! It sounds like the Due Date field might not be on the Edit screen used by the Screen Scheme for the project. So, I would check that first. Are others having the same problem? Or just you?