Trudy P Claspill Community Champion

Olá Júlio, No dia 17 de julho solicitei informações adicionais. Ainda estou esperando por suas respostas. Além disso, se o problema não tiver sido resolvido, você não precisa clicar no botão Aceitar resposta. --- Hello Julio, On July 17 I asked for additional information. I am still waiting for your answers. Also, if you…

I just noticed you have the wrong smart value. It needs to be fixVersions with an "s" at the end. The Fix Versions field is actually a multiple selection field and each Fix Version has multiple attributes (ID, name, release date, etc.). Is your trigger issue going to have more than one value in the Fix Versions field?…

Hello @Wendy Filip What is the filter for this board? Is it limited to a single project? Can you show us the Columns/Status mapping for the board?

Hello @Cory Beaudoin Whenever asking for help with an Automation Rule it will help us help you if you show us the rule you have constructed. It is possible to create a parent Epic issue and its child issues in the same rule, and get the Parent field in the child issues set to the Epic created in the same rule. Seeing the…

Is the rule structure you posted above still accurate? If not, please post new images of your current rule. If so, there are a few things that are problematic in your comment. 1. The {{lookupIssues}} smart value is used only when you have used a Lookup Issues action. Since your rule doesn't include that action, it is not…

Good find, @Ilya Sadukovskiy !

Information from the issue that triggered the rule can be referenced using the {{triggerIssue}} smart value. You can find more information about using smart values to reference fields in an issue here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ Where that document uses {{issue. you would…

@Matthew Busby Welcome to the Atlassian Community. Yes, these changes apply only to the Cloud products. That detail is included in all the referenced documentation and this post specifically calls out Cloud in its title.

issuefunction in issuesInEpics("filter = 163764") That part of your filter is getting you all issues that are children of Epics, from Epics that match the criteria of the filter with ID=163764. What is the criteria of filter 163764? Do you really want to constrain the results to only issues that are children of the…

No, you can't do that. An issue can be associated to only one Active or Planned sprint at a time. Again I have to ask what problem are you trying to solve by associating the Feature to sprints? How do you use the Sprint information in the context of Features? There may be an alternate and better solution to solving your…

You should look for that information on Zoolatech's website. 

프로젝트 유형을 물었을 때 팀 관리 프로젝트인지 회사 관리 프로젝트인지, 비즈니스 프로젝트인지 소프트웨어 프로젝트인지를 언급했습니다. 칸반 보드와 스크럼 보드 모두에서 문제를 발견했다는 귀하의 답변에 따르면 아마도 소프트웨어 프로젝트일 가능성이 높습니다. 팀 관리 프로젝트인지 회사 관리 프로젝트인지 아는 것이 여전히 도움이 될 것입니다. 프로젝트 유형 정보는 모든 프로젝트 보기 페이지에서 확인할 수 있습니다. 백로그가 아닌 스크럼 보드의 활성 스프린트 또는 칸반 보드의 보드 보기에 이슈를 배치하려면 다음을 시도하십시오. 보드 보기에서 열 하단에 표시되는 이슈 생성 옵션을…

Hello @Maximiliano Julio The answer I provided in March is still valid.

Oh, yes, you highlighted that and I missed it. Have you checked the Column/Status mapping for the Scrum board to ensure that all Statuses are mapped to columns, and no Statuses are listed in the Unmapped Statuses area?

Hola @Andrea Arroyo , Esa no es una característica nativa de Jira. Podría crear una regla de automatización que hiciera eso por usted. Hay dos soluciones nativas: 1. Cuando se registra trabajo en un problema secundario, use una regla de automatización para detectar esa actividad y registrar la misma cantidad de trabajo en…

Hello @Ilya Sadukovskiy For the sprint that you are currently showing in the Scrum board, do any of the issues within that sprint actually have subtasks? The Type filter will show only the issue types that are contained in the current sprint. If none of the issues in the current sprint include subtasks, then that will not…

I did leave that detail out, didn't I @Bill Sheboy ? You always provide excellent additional details!

Thank you for that additional information, @Colleen Cosgrove To have a rule triggered by an action in one project and from that cause a change to an issue in a different project, your rule will have to be a Multiple Project Scoped rule. Such rules can be created only by Jira (Application) Administrators. They can't be…

If you add the condition I showed as another condition in your branch that should address your need.

Hello @yousefq When you specify a JQL in the Scheduled trigger, then the actions that follow will be executed for each issue returned by that JQL. I recommend that you take the JQL out of the trigger and instead add a Lookup Issues action to execute that JQL within the rule. Depending on the frequency of the rule a given…

Hello @Ayush Khandelwal Welcome to the Atlassian community. Subtasks get associated with sprints only when their parent issue is associated to a sprint. Do you have any issues in active sprints where those issues also have subtasks? Are you working with Company Managed projects or Team Managed projects? In your filter you…

Hello @Christine Darczyn That helps some, but does not truly show us the connectivity. Can you show us a Feature including in the display the list of stories attached to it, so that we can see how they are attached? Obscure confidential information. We need to understand if you have modified the Issue Type Hierarchy so…

Hello @Colleen Cosgrove Welcome to the Atlassian community. Whenever asking for help with an Automation rule, it will help us to help you if you provide screen images showing us the complete automation rule. It should be as simple as adding this condition:

Hello @Colleen Cosgrove Welcome to the Atlassian community. Have you tried to create this rule yet? Show us what you have so far, and tell us the part with which you are struggling. Are the transitioning issue and the linked issue always going to be in the same project, or might they be in different projects?

Hello @Melissa C Let us assume that the above filter was run today - 2024-07-22. The way you have the filter written currently using Resolved >= startOfWeek(-1) ...will get you all issues with a Resolved date that is equal to or greater than 2024-07-14. That would include issues with the Resolved date on the 14th, 15th,…

Hello @Meredith Halverson Welcome to the Atlassian community. When you say Stories are "under features" do you mean you have renamed the native Epic issue type (the normal parent of a Story) to be "Feature"? Or are you creating a relationship between a Story and a Feature issue type in some other way? Can you show us a…

Hello @Fernanda Donnini Welcome to the Atlassian community. Your post tags indicate you are using the Free product plan. Is that correct? Are you able to edit other fields displayed in the same issue's details? Are you able to edit the field in any other issue? What type of issue is it? What is the status of the issue?

Hello @Gena Urowsky Welcome to the Atlassian community. As Valerie indicated, we are a community of users, so we can't directly access your system and examine the usage ourselves. For that you would need to contact Atlassian Support directly. However in regard to at least this one item: I dug into the automation using the…

Is the user a Managed Account, using a login in a domain that you have claimed? Have you tried the steps in this documentation? https://support.atlassian.com/user-management/docs/make-changes-to-a-managed-user-account/#Require-a-user-to-reset-their-password

Hello @Marsha Miller Your second screen image shows the Permissions Helper screen and you have checked the permissions for a specific issue - DEV-###. Is DEV the key for issues in the InSite Development project? If it is, clicking on the IN: Simplified Permission Scheme link will just take you to the Access page of the…