Comments
-
This document indicates that specified projects can be moved from one cloud site to another: https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/ I have not been through that process myself.
-
Is the Sprint a static value or are you trying to derive that dynamically? Is the list of projects from which issue will be included static, or is that also something you are trying to derive dynamically? Note in Cloud you can't query the database directly. You can use JQL to execute queries. If the Sprint is a static…
-
Hello @Lakshmi Durga Tammineni Welcome to the community. Your post does not include the actual code you are using. What is your hosting type - Cloud or Server/Data Center? You said "after an upgrade" which makes me think you are using Server or Data Center. What version where you using before the upgrade, and what version…
-
Hello @John McDonald Welcome to the community. Team Managed (a.k.a. next-gen) projects are intended to be completely stand-alone. None of the information for a Team Managed project is shared with other projects - not fields, not issues, not workflows. You cannot set an issue in a Team Managed project as a child of an Epic…
-
@Saira Referring to the comments in the issue you posted, a new comment from today says that one person contacted Atlassian Support directly and had Atlassian disable the feature for their site. Other comments indicate there is no way for Jira Admins to disable the feature.
-
Hello @Claudio Pellegrini It appears to me that the information in the related post I referenced applies to your situation. It is a known issue that the Parent field (used in Team Managed projects to note the parent Epic of an issue or the parent issue of a sub-task) is not available to using in the When Field Changed…
-
Hello @Chris Dunford If you are using the generic issue linking function then Jira does not recognize the parent/child relationship between the issues, regardless of the name you give to the link relationship. The only parent/child relationships Jira understands are between an Epic and its child issues, and between an…
-
Hello @Sascha Heinemann From your screen image it appears to me that you are working with a Business type project, as opposed to a Software type project. I don't work much with Business projects, but it has been my experience that the behavior for those is to have a column for each Status in the workflow, and you don't get…
-
Wenn Sie ein Problem anzeigen, das mit einem anderen Problem verknüpft ist, sollten Sie einen Abschnitt für verknüpfte Probleme sehen, der die verknüpften Probleme auflistet. Wenn Sie Ihren Mauszeiger in die Nähe der rechten Seite eines dieser Probleme bewegen, zwischen dem Status und dem Rand der Gliederung, sollte eine…
-
@Fabio Racobaldo _Catworkx_ You are not required to have a Resolution value for a sprint to consider an issue completed. You only have to have the status mapped to the farthest right column on the board.
-
You need to combine the three statuses into one column. If you click on the ... button at the upper right corner of the board, you should see an option to Configure Board. Clicking that should show you the mapping of Statuses to Columns for your board. You need to drag-and-drop the Statuses for Obsolete and QA-Fixed from…
-
Hello @guyot Welcome to the community. Are you working with Jira Cloud Standard and Basic Roadmaps, or with Jira Cloud Premium and Advanced Roadmaps? Or are you using a third party app for planning? Can you provide a screen image of your plan (with any confidential image blacked out)?
-
@Gothandaramanr Also, I just noticed there is a "register for a demo" link available in the Jira Questions forum at https://community.atlassian.com/t5/Jira-questions/qa-p/jira-questions
-
Hello @Richard Oberndorfer Welcome to the community. Advanced Roadmaps allows you to add issue levels only above Epics. You cannot insert a level between Epics and Story. In your image showing the hierarchy, the order you see the issue types listed is the order of the hierarchy. Ignore the numbers next to Epics and…
-
Hello @Jackie Bilog I recreated your issue in my own instance. Then I found this post that talks about resetting the date formats for your system to use 4 digit years. If you do that it solves the problem. https://community.atlassian.com/t5/Jira-questions/2029-Date-Bug-Fix/qaq-p/630830 credit to @Andy Heinzer
-
Hello @Charles Frankston Welcome to the community. Have you contacted Atlassian directly about this? It is an interesting idea, and I wonder if anybody has raised it with them. If not, you should!!
-
Hello @livia.fialho Welcome to the community. Are you working with Software projects? Are the projects Company Managed or Team Managed? If you are working with Company Managed Software projects, then as @Alex Koxaras -Relational- said you can modify the filters used by the boards to show issues from other projects, and in…
-
You will have to map all three statuses into one column - the column farthest to the right - in order for the sprint to consider issues in all those status as "completed".
-
Most of the people in this community are just other users of Jira. If somebody from Atlassian responds, you'll see "Atlassian Team" next to their name. There are also members who are employed by companies that have apps in the Atlassian Marketplace, and they will sometimes have "Marketplace Vendor" after their name.
-
You also may find the information in this post helpful. https://community.atlassian.com/t5/Jira-Cloud-Admins-discussions/Automation-Rule-Triggered-by-Change-in-Parent/td-p/1724967 credit to @Mykenna Cepek
-
Hello @Claudio Pellegrini Welcome to the community. Are you working with issues in a Team Managed project or a Company Managed project? Are you looking at sub-task type issues or issues that are children of Epics?
-
Hello @Ebe Welcome to the community. If you are using the native Jira CSV import functionality you can use whatever names you wish for your headers in your CSV, with limitations. As you use the import wizard you will see that there is a step where you provide a mapping of your headers to the corresponding Jira fields to…
-
Hello @Máté Gász What is the relationship between PRO-1 and the issues in the other workflow? Are they linked? Are they Epic and children, or issue and sub-tasks? Or is it always going to be specifically PRO-1 that you want to update? Never some other issue? The answers to those questions are required to recommend a…
-
Hallo @Andreas Schrödl Willkommen in der Community. Es gibt keine Option, um die Erstellung des Links beim Klonen zu verhindern, wenn die Klonaktion ausgeführt wird. Sie können die Verbindung zwischen den beiden Problemen nur im Nachhinein entfernen. Sie könnten eine Automatisierungsregel einrichten, um nach Klon-Links zu…
-
No, there is no way to specify that a Component in one Project is represented also as a separate Project.
-
There is an issue In Progress in Atlassian's worklog related to this: https://jira.atlassian.com/browse/JRACLOUD-79371
-
You could use an Advanced Search Issues filter to find all the closed issues that have no value in their Sprint field and use the Bulk Change feature to update the Sprint field in all the issues to a Sprint of your choice. If that is an "active" sprint, then you should see all the closed issues appear on the Board, I…
-
I see the same behavior. So far I have not found any mention of this being a known bug. Have you tried contacting Atlassian Support directly about this? https://support.atlassian.com/contact/
-
Hello @Scott Buratt There is not a configurable setting for this. The fundamental concept of a backlog is that it is work that remains to be done. There is no need to display work that is already done in the backlog. Your backlog would eventually grow to be an unmanageable list. What problem are you trying to solve by seen…
-
Hello @Chrys Piva Welcome to the community. I think you have misunderstood. A sprint does not evaluate the issues as completed based on the Resolution field. It determines that issues are completed if they are in a status that is mapped to the column farthest to the right on your board. It doesn't matter what the status is…