John Funk Community Champion

Hi Neil - Welcome to the Atlassian Community! Can you share the rule that you have (screenshot)? And the Audit log for when you run it?

Well, I forgot that you were on Server, so you with need a plug-in like Automation For Jira or ScriptRunner. I don't use ScriptRunner so I would not be much help with that tool. 

Can you show another screenshot with an example? 

Yep, that should do it. :-)

Hi Matthew, The Initiative issue type is not a native issue type in Jira - you will need to create it. https://confluence.atlassian.com/jiraportfoliocloud/configuring-hierarchy-levels-828785179.html

Hi Lara, Your filter uses Epic Link, which is not a field in Epics. So, you are leaving out all Epics when you use that field in your filter. So I would suggest something like this: project = XX AND ("Epic Link" IN (Epic key 1, Epic key 2, .. etc.) or issuetype = Epic) ORDER BY "Epic Link"

Hi Julie - Welcome to the Atlassian Community! It sounds like a timing issue to me as to when the subscription ran and when the issue was acced to the sprint. Maybe run it more than once a day? I see an option for every 3 hours. I know that's a bit much, but it depends on how quickly you want to see that something was…

Hola Mario, ¿Puede proporcionar más información? ¿Qué has hecho hasta ahora? ¿Y qué estás tratando de hacer?

Hi Meagan - Welcome to the Atlassian Community! Cards for Sprints are only considered Done or Complete if they are in the very last column on the board (far right), regardless of the status the card is in. So you need to map your "Ready for Integration" status to the very last column of the Sprint board. 

Thanks for the post @Marc Dvorschak - well done! For me, it would be a trip to Narnia. And it might just be a permanent stay. :-)

Hey @Howard Choularton and @Norbert Grzebieniarz Did you ever get this resolved?

Automation for Jira for sure. 

Hi Joe, JWM is the base Jira product. And then Jira Software is added on top of that. So they will always have JWM. But you can control access using the Permission Scheme(s) used by the JWM project(s).

How do you know if the original assignee is an eningeer or not? You might want to add a custom field that captures a value when the assignee is an engineer. Then in your query, you can check for that value. 

And you are saying that with that query above on the board, you still see completed Epics???

Ah, that might be the problem. Jira doesn't like it when you paste in there sometimes. Try typing it from scratch and see if it will let you execute and save it. 

It should not strip the parens in the area where you are saving the filter. That's a totally different query without the parens. What are the exact steps you are doing after you put in the parens and execute the query? 

That's the problem then. Is this in the Advanced search where you save the filter? 

Can you share a screenshot of the query in the board settings?

It shouldn't - I have tested it on my instance. Did you type it EXACTLY as I have it? 

Hi Edward - Welcome to the Atlassian Community! Have you added the fields to the screen(s) used in the project?

Hi Joe, Maybe try: Project = ABC and (issuetype = Epic and status in (Backlog, "In Progress")) or (issuetype != Epic and statuscategory = Done)

HI Ronnie, What permissions do you have? Are you a Site Admin? Are you an Organization Admin? 

@Sekhar Chandra - Go to Settings > Issues > Field configurations

Hi Rocsana, Make sure you have the Manage Sprints permission in the Permission Scheme for the project. 

Hi Eric, You are correct that Roadmaps can only be used with one project. However, with a Premium Subscription for Jira you get the Advanced Roadmaps tool which can span multiple projects in a single roadmap. 

Hi @Yichen Liu - I would open a support ticket with Atlassian to see if the email address has been blacklisted with Atlassian. https://support.atlassian.com/contact/#/

Hi Danielle - Welcome to the Atlassian Community! You can do a query such as Project = ABC and status changed from "Ready to Release" to "Code Review" You can set up an automation rule to email you wen that happens. Or you can do a filter with a subscription that would email you once a day. 

I took out the brand because it was not needed. Glad you got it working. 

They are associated with the ticket/issue itself and not the workflow.