Trudy P Claspill Community Champion

@Alexandra Papadimitriou Welcome to the Atlassian community. First, please confirm the type of your project. Go to the Projects menu and select View All Projects. Find your project in the list. What does it say in the Type column? Does it say "Team-managed"? If so, be advised that you can't add screens to workflow…

I'm glad you were able to get an answer! Can you provide more detail about the update and how it broke your board, in case another user with the same problem comes across this post? Did Atlassian tell you about any publicly accessible Jira issue that they have created that we could review?

Hello @Srikant_Vijayendran If my response has helped you solve your problem, please consider clicking the Accept Answer button to mark your post as Solved.

Make sure that you check the workflows for all issue types that are included in the sprint. Also make sure that you double check what issues were included in the sprint. To do that you need to go to the View All Issues page under the Filters menu and search for sprint=<the name of the sprint you're trying to close> It is…

Hello @Mark Herschberg Welcome to the Atlassian community. Permissions apply to a project, not a board. If the user has the Browse Projects permission in a Permission Scheme then they will be able to see all the projects that use that Permission Scheme. In addition, if there are any Team Managed projects in your system…

Hello @Demi Hotahot Welcome to the Atlassian community. That indicates that the issue was in two previous sprints that were completed, but the issue itself was not completed in those sprints. The only way to remove that information is to reopen the specified sprints, remove the issue from the sprints, and then re-close the…

Привет @aybekataev2 , Добро пожаловать в сообщество Atlassian. Какое отношение ваш пост имеет к продукту Atlassian под названием «Jira»? Этот форум предназначен для вопросов о «Jira».

You need to use the text you see in the Linked Issue section that shows the relationship between the Parent and the Epic - "child of"

I'm glad I could help you. If my response helped you solve your problem please consider clicking on the Accept Answer button to mark you post as Solved.

Hello @Gopikrishna Mamidipudi Welcome to the Atlassian community. Do you want to require that some amount of time has been logged against the issue at any point in the past? Or do you want to require the user to log time against the issue at the same time the status is changed to Done?

Since your Parent and Epic issues exist in different projects you will have to create this rule from the Global Automations screen. You will have to set the Scope to Multiple Projects and you will have to set Projects to all the projects that could be involved. You may want to add a Condition after the Trigger to proceed…

Hello @Kevin Lu #1 In order to limit the users to seeing only that one project you will need to review the Permission Schemes associated with all your other projects and ensure that the external users are not assigned to any User Group that has been granted the Browse Projects permission and that the Browse Projects…

Hello Greg, This is a puzzler. You can contact Atlassian support by opening a case at https://support.atlassian.com/contact/#/ I don't think that the Jira Product Discovery product would cause this problem, but I don't work with that product so I can't be certain. The Assignee avatars should display the logged in user and…

Obrigado por essas imagens. Posso ver nessas imagens que o projeto é um projeto de Software Gerenciado por Equipe com as opções do quadro Scrum (Backlog e Sprints) ativadas. Os outros projetos que você vê na Linha do Tempo também são projetos de Software Gerenciado por Equipe? Você disse que migrou de uma conta para outra.…

Correct - if either one of the projects is Team Managed, the parent Epic and child issue must be in the same project. Correct - if both projects where Company Managed, then the parent Epic and child issue can be in different projects. However, if you are considering trying to change to Company Managed projects, that comes…

Hello @Gopikrishna Mamidipudi Welcome to the Atlassian community. Please provide screen images of the rule you have created and explain how the results are not what you expect. Please also provide screen images showing the details of the Audit Log for the rule execution.

Hello @Dailet Are the blocking issue and the blocked issue in the same project? This rule should work for you. Adjust the status values I've used to match your needs. The rule is triggered when an issue transitions to Done. It starts a branch to look for any issues linked to it with the "blocks" link. For each of those…

Hello @Susheela_Kushwaha Was your account created through integration with an Identity Provider? If so, then the data is being managed by the identity provider and must be changed there. You can edit your own Atlassian Account information only if you manually signed up for your account in Atlassian Cloud directly and you…

Hello @Ersula Igori As per this documentation, you are correct. Fields on the View screen but not on the Edit screen should be visible when viewing an issue. Have you checked the More Fields panel below the Details panel on the right? Is the field shown is the issue layout?

Hello @Mahesh Joshi Welcome to the Atlassian community. Jira has some automation features available. Automation Rules can be used for many things. The permission to create Automation Rules has to be granted by Jira Admins, and can be granted based on User Groups. You would need to delve into the specific requirements of…

Hello @Ellyot Rhee Welcome to the Atlassian community. When you create an issue type within a Team Managed project, that issue type is unique to that one project and cannot be shared with other projects. That is the nature of Team Managed projects. The customizations within Team Managed projects can't be shared with other…

Hello @John Roca Welcome to the Atlassian community. Can you confirm for us please the type of project you are using? Get that information from the Type column on the View All Projects page under the Projects menu. Can you provide screen images of you trying to group by Category but it is not appearing? There is a native…

Hello @Sean Saxon Welcome to the Atlassian community. Yes this is possible. Create a separate transition to the Won't Do status that does not include the Validator. On that new transition set the Condition for Hide from User. That will make that specific transition available only to Workflows and the REST API. Automation…

Hello @Rajat Samseriya Navigate to your Service Management project and select Project Settings, then Email Requests. The page that displays has information about the Reply-To email address used in notifications generated by the project. There are links on that page that will bring up more information about changing the…

I found this KB about enabling customers to reply to Automation-generated emails and have the replies get added to existing JSM tickets as comments. https://confluence.atlassian.com/jirakb/replying-to-email-notifications-from-the-automation-rule-to-be-added-as-comments-to-existing-issues-1255445743.html But you said the…

Hello @Garry Raymond Bryan Suwu Welcome to the Atlassian community. Have you tried looking in the Billing section of https://my.atlassian.com ?

Hello @James Dushay That is functioning correctly. On what are you basing your expectation that Tony's manager should be able to be mentioned without first being a Request Participant?

Hello @David Quiram I don't think I am understanding the issue you are encountering. Can you provide an example of what you mean by "and doesn't iterate over it again to process those included smart values. "? What smart values are missing? Can you show us the entire Automation Rule, please? Sometimes the problem is…

I would like to add some key points to this. If your teams are using Jira Service Management projects to interact with customers, anybody that needs to change the issue status or add comments that will be visible to customers must have a Jira Service Management Agent license. If they have only a Jira license they will not…

Hello @Srikant_Vijayendran Welcome to the Atlassian community. To have access to extend the Issue Type Hierarchy above the Epic level you must have a Premium or Enterprise plan for Jira. Do you have that? If you have that, then a Jira Administrator needs to create a new global issue type for Initiative and add it to the…