John Funk Community Champion

Nope, not possible. 

Hey @Sreenadh - Yes, it is a required field so it will always default to something and that cannot be changed. If you have not dedicated a default, it will always use the first issue type in the Scheme attached to the project. Or sometimes it will use the one most recently used. 

Yeah, that view is very limited for any kinds of custom queries like that. The other possibility is to create a second board and then you can do those kinds of things. It just won't be a List view. Here's an article I wrote earlier this year on how to do that. If it's helpful, please give it a Like.…

That's easy for me - fall/autumn! (no intended dig to @summer.hogan ) The color of the leaves were especially beautiful this year and the time stretched further than usual as we typically only get a couple of weeks of really good Fall weather. 

Hey Blaine - Welcome to the Atlassian Community! What type of project are you using? Components are not currently available for Team-managed projects.

Let me see if someone from Atlassian can come here to check on you. 

I love the idea of posting a video update. Thanks @Abby Stiris !!!

If that's the case - then how are the issues connected?

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

Sure - here is a link where you can search for Partners: https://partnerdirectory.atlassian.com/ And being up front, I work with an Atlassian Gold Solution Partner called Fringe Technology. You can request training information here: https://fringe.atlassian.net/servicedesk/customer/portal/16/group/40/create/133

Hi Joshua, I don't have time to fully investigate right now, but here's some thoughts. 1. You should be able to do this now. Just make your trigger as a Field Value change to Assignee and send the mail to the Assignee. 2. I am thinking that you could use the #lookupIssues function in some way to get the account ID of the…

Hi @Sreenadh Currently, you cannot add custom fields to the JSM built-in notifications. You can vote for and follow the request here: https://jira.atlassian.com/browse/JSDCLOUD-4642 Alternatively, you can create a notification using Automation For Jira. 

Hi @SockBlocker Are you able to update the issues through a Bulk Change and clear the Epic Link for those issues? You would do the query based on the children. 

Hi Mike, You don't have to re-create and export all of the tickets. If there is development work being done, it should be done in Jira Software. So you can have both types of projects and if an issue requires development, then you can clone it into the JSW project using automation and link the tickets together. Otherwise…

Without testing a lot - that's what I would do. The hyperlink is the same so it doesn't matter if you have one that includes the whole thing including the space or have two separate - I don't see a difference in that. 

Hi Low, Maybe try "Epic Name" ~ "Release A"

<a href="{{issue.toUrl}}">{{issue.key}}</a> <a href="{{issue.toUrl}}">{{issue.summary}}</a>

Hi Lodovico - Welcome to the Atlassian Community! You might try a different browser or try using Incognito mode to see if it works with that. 

Hi Elmer, You can't set a predefined filter for the List. You might want to vote for and follow this request: https://jira.atlassian.com/browse/JWMCLOUD-173

Hola @kevin Muñoz ¿Alguna vez resolviste esto?

What I did in those cases was to create a new Group which I called Automation Administrators. And then placed the people in that group. Finally, I added that group the to the global Configuration in the drop down there. Still not sure if they would be able to administer multi-project rules even if a project admin in both. 

Hey Mary, There are Atlassian Solutions Partners that can do that for you and some freelancers as well. 

Hi Jeanna, I don't think anything has changed recently with the way global permissions are setup for automations. Can you share the Global Configuration that you have set? Also, keep in mind that if you have a rule with multiple projects, a project administrator must have project admin permissions on ALL projects used by…

Yep - see Trudy's response. :-)

Glad I could help!

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

Hi Shea - Welcome to the Atlassian Community! Scheduled triggers for automation can basically run the same filter - just post the actually query of the filter in the JQL part of the scheduled trigger. 

I would set the value of some type of field when the issue moves to Publish the first time. Then you can have the trigger based on Issue Transitioned to Publish. But you can then add a condition to check the value of the field so that it will know when rule to finish firing. 

Hi Martin, Is there an automation rule that fires on both transitions? And they just do different stuff?

Great! Glad you found a solution.