Trudy P Claspill Community Champion

Hello @Hoa Walsh Your syntax is incorrect here: If you want the header text to appear only once, put it before the {{#lookupIssues}} tag. Between the {{#lookupIssues}} and {{/}} tags list just the field names and don't use curly braces. Ticket,Created,Assignee,Requestor,Summary,Last Comment.Resolved {{#lookupIssues}}…

The community is not a paid support team. We all do this voluntarily. There is not a general option to schedule time to meet live with community members. Help is generally provided asynchronously through the community posts. You can certainly ask responders if they are willing to meet with you. Or you can open a support…

Hello @Rita Arellano Depending on you Jira version you can use the Lookup Issues action to get the issues linked to the Epic using a JQL statement. Look for that action in the Automation Actions documentation. If it is available it will also show the syntax for listing each issue in the result set.

Hello @Hoa Walsh When you put the JQL in the Scheduled trigger then the actions in the rule will be executed for each issue. Instead put the JQL in a Lookup Issues action. You can then add the entire result set into one email using syntax like this {{#lookupIssues}} names of fields in the issue {{/}}

Let me repeat back what I think you want. * When an issue is created * And it is an issue type that could be a child of an Epic * And it is not already a child of an Epic * And it has just one value specified in the Components field * Then find the Epic that has a Summary that contains the name of the Component * And if it…

Hello @Jimmy Hardina Welcome to the Atlassian community. Are the excluding subtasks all of the same type? Start by checking the filter that is used to select issues for the board. Ensure that it is written in such a way that the subtasks issue types are not being excluded. Find the filter by clicking on the ... button in…

Hello @Avani Mahadik Welcome to the Atlassian community. Access to the agile board is based on the people with whom the board filter has been shared. To limit who can access a given agile board, change who the underlying filter is shared with. Refer to: https://support.atlassian.com/jira-software-cloud/docs/manage-filters/

Hello @Matt Caruso Is your end goal only to get an alert when all the child issues are closed, or to close the parent Epic automatically? A rule like this could work for you. Trigger: When issue transitioned to Resolved Condition: Issue Type is one of the types that can be a child of an Epic Branch: For Related Issues /…

Hello @Jason Chayer Automation rules are the "native" method to accomplish that requirement. On a Standard subscription plan you should have up to 1700 automation executions per month. How have you determined that you have "only a few" automation triggers a month. Also, just because a rule is triggered does not necessarily…

You did not answer my first question: When you say you want to create a new column on the board do you mean you want to add a new Status value to which you can set the issues? I am going to assume that you mean you want to add another Status. With a Company Managed business project you have to add the Status to the…

Hello @[deleted] But still I was able to move tasks on CM DEVELOPMENT board. What do you mean by "move tasks"? Your original post says: But, the project managers must not be able to complete the sprint. Moving a task is not the same thing as completing sprints. Additionally, according to the tags on your post you are a…

You might be able to do something like add the Fix Version name to the Sprint description, and then have an Automation Rule that runs based on Sprint Completion, that parses out that data, finds the corresponding Fix Version, and sets the Fix Version for each completed issue in the Completed sprint.

Hello @Rohith k You cannot add a second "Parent" field. You can add the Linked Issues field to the screen and that would give you the ability to link the issue being created to other issues by entering the other issue's key. You will have to ask your Jira Administrators to make that change. I have no access to your…

There is still a critical piece of the puzzle that you have not answered - the directionality of the link between the issues. This is important because it will determine which issue is gets updated. You have said that Go Live depends on Warranty. Based on the screen image you presented when you view Warranty you see: "is…

Hello @Dmytro Komlyk Why must you use Create Issue with Request Type? An alternate solution is to set up a separate rule for the actions of the second branch. In the current rule add some unique value (unique to this rule) to each of the issues that is created. Then set up a second rule that is triggered by issue created,…

Can you provide screen images show the rule you have constructed so far, in English? Otherwise can you describe each step in the rule? You mentioned in your reply that you are using a branch, but a branch should not be necessary. You can use Smart Value conditions to look at the information in the trigger issue's parent…

Hello @8Crafter Are you asking with regards to the Free Jira product or the Free Jira Service Management product? The site that you referenced appears to be using Jira Server or Jira Data Center, not Jira Cloud. With a paid subscription for Jira Cloud you could enable public/anonymous access to your project. With the Free…

Are those screen images of your own access or of what is seen by the PMs that use this project? To what Roles in the project have you assigned the PMs?

Hello @Max_Clark Do you have permissions to create links in both the source and destination project? What information is available from the rule execution audit log?

Hello @Pushkaraj Thakurdas Welcome to the Atlassian community. You can use Automation Rules to create the Sprint, and the Epic and its child tasks on a schedule. https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ You can use the Create Sprint action to create the sprint. I would recommend you use a…

Olá @paulo paz , Bem-vindo à comunidade Atlassian. Se esse projeto existir em um site Jira diferente que usa um URL diferente e você não for administrador desse site, não será possível acessar o recurso nativo para copiar o projeto para um site diferente. Se você ainda tiver acesso aos dados do projeto nesse site, poderá…

Olá @Luiz Renato Reina Martinelli Bem-vindo à comunidade Atlassian. O gráfico Sprint Burndown será alterado apenas por questões de nível padrão (não subtarefas) sendo movidas para dentro e para fora da coluna mais à direita em seu quadro de scrum. Os gráficos nativos não podem ser alterados para atualização com base na…

Hello @Jodie Parsons You appear to be working with a Team Managed project. First question - do you want the users to be able to select multiple values at once for Severity such that an issue could show both Critical and Medium in that field? Or do you want them to be able to select only one value? I suspect you want them…

Hello @Sushil Ranjan An issue can have more than one Component value at a time. What should happen if the issue has both component values? Are the issue keys for the Epic known, or does the automation need to find the Epic based on the Summary?

Hello @Mateusz Janczewski Welcome to the Atlassian community. Can you provide a screen image of the backlog, pointing out a subtask and its parent issue, so that we can see what you see? Obscure other confidential information.

Hello @Kevin Lu Do you want to impose this only on the Create Issue dialog, or do you want to hide all Form4 issues from those other users? Have you seen this article? https://confluence.atlassian.com/jirakb/how-to-restrict-issue-creation-for-a-particular-issue-type-based-on-roles-in-jira-server-960701303.html

Hello @Bindu Shrivastav Whenever you ask for help with an Automation rule it will enable us to help you more efficiently if you provide screen images showing the entire rule. The focus of the rule has to be on the trigger issue in order to edit the trigger issue. A branch is probably not the right component in your use…

Thanks, Chris!

For an Automation Rule to create the link you would need to specify and event that would trigger that rule, such as the creation of the BA Tsk issue. You would also have to somehow identify the issues that need to be linked. How would the rule know the ticket to which the Task should be linked? Are you recording the ticket…

Hello @이진주 Welcome to the Atlassian community. Have you tried to create this rule? Which elements are you unable to figure out? Please show us what you have so far.