Trudy P Claspill Community Champion

@Relja Mihajlović Have you tried changing the subscription on that product from Standard to Free?

That sounds familiar - a problem with selecting issue types in a Condition when the rule is scoped for multiple projects. I'm not currently finding where I read about that before, though.

Glad I could help @Jamie Jacques Please consider clicking on the Accept Answer button to mark your question as Solved. That helps others searching for answers find the posts that have validated solutions.

Take a look at this post. https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-Jira-Clone-Epic-Story-and-Sub-tasks/qaq-p/1719652 It talks about cloning Epics and their children, and subtasks, but it should give you enough information to use it as a base with modifications to create your rule.…

Hello @Tomas You have the Link Issues action occurring in the rule before the steps that create issues 625 and 626. The action cannot create a link to issues that do not yet exist. You need to eliminate that action, and instead structure your rule to have a branch after the Create Issue actions and but the Link Issues…

1. Immediately after the trigger I advise you to add a condition to check the issue type of the trigger issue and ensure that it is a "book" (or whatever name you are using for that issue". Manual automation rules can be triggered from any issue type, and this could fail if triggered from. other issue types. 2. The first…

This post identifies an api that will give you all the people and groups assigned to a specified role in a specified project. https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-project-roles/#api-rest-api-2-role-id-get It will return output that lists each group assigned to the role and each individual…

So does that mean there are only two layers? Do you not use Sub-tasks below the Story/Task/Bug/Spike level?

Hello @Tomas Welcome to the Atlassian community! Please show us a screen image of the rule and the details of the Link Issue step. In the Link Issue step the rule is trying to create a link between the issue in context at that point in the rule, and the issue you identify in the configuration of that step. The error…

You can find out when an issue was transitioned to Complete by reviewing the History information for the issue. There is a tab for that at the bottom of the issue view screen in the same area as Comments. There was a time when issues transitioned to green/done statuses specifically in JEM projects were not automatically…

Hello @Sharada Thota What document are you following for instructions to load sample data?

Hello @Shravani Moosaramthota Welcome to the Atlassian community. I have not heard of any limit to the number of Sites/instances of Jira under an organization. But you should carefully consider whether or not having multiples Jira instances is a good idea. Access for each one has to be managed separately. They won't share…

Hello @Will Henry Are you using the Timeline option from the panel on the left when you are viewing an agile board/backlog? Or are you using the Timeline option that is available from an Advanced Roadmaps Plan, accessed from the Plans menu? Have you looked at the history of the specific Epic you are modifying? Check if it…

Hello @Jamie Jacques Welcome to the Atlassian community. The first question is are you using Jira Cloud or Jira Server/Data Center? If the URL you access is like https://something.atlassian.net then you are probably accessing Jira Cloud. If your URL is different then you can check if there is a version number displayed at…

Can you provide a screen image of what you see in the Automation rule, and the custom field definition showing the value available?

Olá @Marcella Vieira , Bem-vindo à comunidade. O Jira não oferece suporte à exibição de registros de tempo individuais como resultados de um filtro. Os filtros são projetados para retornar problemas. Jira não possui relatório nativo para gerar registros de horas. Você precisará de um aplicativo de terceiros para isso. Você…

Hello @Olexandr Babych Have you investigated the API information for Permissions? https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-permissions/#api-group-permissions

Hello @PIERSON Cédric That is not a native behaviour of Jira. It could be caused by an Automation Rule, or a Listener, or a function provided by a plugin such as a Behaviour from the ScriptRunner plugin. Without knowing what plugins you have on your instance, we can't suggest what might be causing it.

What is your issue hierarchy? How many layers are there below a Feature? Do you need to clone all the layers?

Hello @Sarah Isaacs With what type of project are you working? Get that information from the Type column for your project's entry on the View all projects page found under the Projects menu. When you look at the Rule Details page for this rule, what does it show for Scope and Projects? For the project(s) in scope for this…

Take a look at this: what are external sprints in advanced roadmaps (Found by using google to search for (jira cloud "advanced roadmaps" "external sprint")

I believe those colors correspond to the Status Category of the issue on the same line. Gray = To Do Blue = In Progress Green = Done Every individual possible Status value that can be used on an issue is created in one of the three above Status Categories. The Status itself will show the same color coding to indicate the…

Hello @Eduardo Lello It should be "fields", not "field". Can you check your environment to see if you have more than one custom field named Category defined for the system? You can determine this by going to the View all issues page under the Filters menu, then enter a JQL statement. Start typing in category and Jira will…

I'm glad I was able to help you. If all your questions have been addressed, please consider clicking on the Accept Answer button. This helps other people searching for answers find the posts with validated answers.

Teams are now accessible on other instances within the same Organization. When a user is logged into an instance they can see the Teams that have been set up on any instance within that Organization. With this change, Teams have been elevated from site specific to shared at the Organization level. As such you now must be…

There is a change request about this to which you can add your vote/comments. https://jira.atlassian.com/browse/JWMCLOUD-19 You could also consider creating a saved filter for the project, then creating an agile kanban board from that saved filter. The agile board allows for more customization of the timeframe for hiding…

Adding to this... @Jamie.Humphreys Is your project Team Managed or Company Managed? The referenced documentation applies only to Company Managed projects. Issue Security for Team Managed projects is very different. In that case, issues are restricted to project Roles.…

That is an interesting work around!

Hello @dkwan JWM projects are hard coded to hide completed issues when they have been in that status for 14 days or longer. This is not configurable. What problem are you trying to solve? And what timeframe do you want to use?

Hello @SHEHZADALI ISMAILY What is your issue hierarchy? How many layers are there below a Feature, and do you need to clone all the layers? Are you willing to consider a third party app instead of using Jira Automation?