John Funk Community Champion

Yes, but I mean have the user directly click on the link. Go to Filters in the top nav bar and then find the filter and select it. Then just copy the URL address and send that to the user. If they can click on the link you send and see results, that might eliminate the most obvious. 

Probably just better off using one of the add-ons like Deep Clone. 

Hmm, that's beyond me. It's probably time to open a support ticket with Atlassian to see what they say. https://support.atlassian.com/contact/#/

Okay, thanks for the clarification. Let's see what we can do. Maybe add the comment to the Parent and copy it down to all the children under a branch? 

Hi Ryan, This is typically the error you seen when they don't truly have permissions to the underlying filter. Maybe send them the link to the filter itself and see if they can execute it and see results. 

Hey Courtney, Well, that's weird. I would go ahead and open a support ticket with Atlassian to see if they can help. Otherwise you could chase a lot of rabbits. https://support.atlassian.com/contact/#/

Hi Adil, You can't assign an issue directly to the Component Lead using automation yet, but there is a workaround that you can find here: https://community.atlassian.com/t5/Jira-Service-Management/Is-there-a-smart-value-for-Component-Lead-Lead-Developer/qaq-p/1458713 If you create the custom field and then an automation…

I don't image that will be any different than using the Parent branch. Maybe add an IF/ELSE condition block and put one Parent branch under that and another branch for Epic under it. 

Pretty positive that you will not be able to do that in the Cloud version. 

Hi Zaldy! Not in a screen, but you can do it with a Proforma Form. 

And what are you trying to update in the parent? You might try a Branch for Parent then action for Edit Issue under the branch. Then for the field you want to update, use {{triggerIssue.Custom Field}} for the value of the custom field you want to copy up. 

Привет, sapr0nov, Что вы используете для названия вашей ветки? Как вы его строите? Это основано на Резюме карты? Если это так, то не будет ли просто иметь другое резюме, чтобы предотвратить дублирование ветвей?

Hi Shena - Welcome to the Atlassian Community! Try clearing your cache or using a different browser to see if that solves the problem. (Or open a browser session with Incognito). 

Yeah, I think that's where Atlassian will need to help. 

Ah, I understand now. But also, I am not familiar with how the Triggers are processed in the workflow and what user it thinks did that. You probably need to open a support ticket with Atlassian to see if there is more information available. If you end up doing that, please post back here with the solution. Otherwise, you…

Hi Anty - Welcome to the Atlassian Community! So are you just trying to handle the scenario when the Epic itself is deleted? If so, then just add a Condition for Issue Type - Epic under the trigger. If you are deleting a story under the Epic, I don't think want/need anything to happen. That would take care of it. 

Hi Ethan, The people who show up on the board are users who are currently associated with at least one card on the board - either as Reporter or Assignee. So if you replace the Reporter and Assignee fields with only current active users, then the inactive users should disappear from the list. 

Hi Just1ce, Can you not just use {{issue.Request Type}} ?

Sorry, I am not following this at all. Can you give a step-by-step scenario that you are doing and what you want to see? 

So, what is not working? What are you expecting to happen that is not happening? 

Hi Chandra - Welcome to the Atlassian Community! Can you share the rule that you have so far? 

How are you adding/accomplishing this message?

You can create a filter to identify those issues so you can do a bulk change. Something like: project = ABC and status changed to "Backlog" from "Done" by currentUser() after startOfDay()

But why? What does that buy them? 

Roadmaps are project specific. If you want a roadmap that spans multiple projects, you will need to create an Advanced Roadmap - but you will need to have a Jira Premium subscription to create that. 

Hi @Support Team No, you can't do that directly, but you can control who can Create Issues on a project using the Permission Scheme. If the user cannot create issues or does not have the Browse Projects permission, they will not see the value for the Project in the Create screen. 

Hi @IS KSA Team - Welcome to the Atlassian Community! Yes, for now, Jira Work Management is included in your subscription to Jira Software Cloud. Atlassian has hinted that there will be a separate subscription required for JWM starting around April of 2024, but we don't have details yet. 

Well, that formula seems correct to me - 29-26 is 3. What are you expecting to see there and why? 

Hi Dhiman - if you would, please include all of your comments in this comment thread so that readers will be able to follow the conversation. What do yo mean by "common message"? Do you want to update fields in the other sub-tasks based on the information that was updated in the sub-task that got changed?

Hi Dominic - Welcome to that Atlassian Community! I assume you added a new workflow to the workflow scheme and did not select a single Issue Type for the workflow when you added it. And therefore all issue types for the workflow scheme got changed to the new workflow. Correct? You can go back into the Workflow Scheme in…