Comments
-
Can you provide more information? Is this part of an Automation rule? If so, can you show us the rule? And what information is provided in the Audit Log for the rule?
-
Hello @flacoursiere Welcome to the community. Did you add your new custom field to the Field Configurations (for the various issues) used in the Field Configuration Scheme assigned to the project? Have you checked the Issue Layout to see if the field is Hidden When Empty?
-
Hello @Mélanie Liguet Welcome to the community. The answer is No. As per the documentation https://confluence.atlassian.com/adminjiracloud/archive-a-project-1013843066.html "When a project is archived, its issues won’t appear in basic or advanced search results. " For Company Managed projects the work around we have used…
-
The issue type hierarchy in the Standard plan for Jira Cloud is Epic < Story/Bug/Task < Sub-task You are allowed to create additional issue types, but only at the Story/Bug/Task and Sub-task levels. If you need to extend this hierarchy like this Initiative < Epic < Story/Bug/Task < Sub-task ...you will need to either…
-
In the Issue Layouts screen you will see 1. The issue types available in your project 2. Those issue types grouped by the Screen configuration they use. In the image you've shown us 1. Feature is not shown. That leads me to believe that Feature is not an Issue Type available in this project. 2. The issue types Story, Epic,…
-
Hello @jacob_paul Welcome to the community. Do you have separate Screen configurations for the feature and epic issue types? I have not used the Project Settings > Issue Layout before, but I see that it says * Where issue types share the same screen configuration, you'll edit their field ordering together and they'll…
-
Be advised that if you delete other boards in which sprints were created, those sprints will also be deleted.
-
I set up a test project with an active sprint and issues assigned to 7 different people and some issue unassigned. I get 6 people avatars displayed plus the avatar for selecting unassigned or the 7th person. Are you sure that the avatars shown on the individual cards are for the Assignee? Maybe a different User Picker…
-
If you can find out your Jira Cloud subscription plan type (Standard vs. Premium) that will tell you which Roadmaps version you have (Basic vs. Advanced). We have the Standard plan so I can see only what is available for that. From this document... https://www.atlassian.com/software/jira/features/roadmaps?tab=advanced…
-
I thought it was mentioned somewhere. Perhaps it comes up in the screens when the Move Issue feature is used. I can tell you from experience that the links between Epics and their children are not maintained. Also, in Team Managed projects you cannot edit the Parent field directly like you can edit the Epic Link field in…
-
No. Refer to this document for more information on migrating/moving issues between Company Managed and Team Managed projects https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/
-
According to this page https://marketplace.atlassian.com/apps/1212136/advanced-roadmaps-for-jira-software-formerly-portfolio/version-history it seems like there is some version of Advanced Roadmaps that is available for Jira Server and Data Center, but I am unclear how you actually get it.
-
When you are building a dashboard, all gadgets are available. The dashboard is not inherently for a Company Managed project or a Team Managed project. The gadgets may work differently or not at all for a Team Managed project because its architecture is different from a Company Managed project. I haven't check all the…
-
Epics cannot have other Epics as children. The native hierarchy supported by Jira is Epics < Story/Bug/Task < Sub-tasks You can extend this hierarchy using something like Advanced Roadmaps or other third party apps. The percentage complete, based on issue count, for an Epic is displayed within the Epic itself. You can see…
-
You do not have to migrate to a Team Managed project to access Advanced Roadmaps in Jira Cloud. Advanced Roadmaps is available for Company Managed projects in Jira Cloud. If you are considering a migration from Jira Server to Jira Cloud, you should review the resources available that discuss that migration, such as this…
-
I concur with @Nic Brough -Adaptavist-
-
Next Gen projects are a concept available only in Jira Cloud, to my knowledge. If you have some reference that says Next Gen projects are available on Jira Server, please share it. As mentioned in another post of your, Jira Premium is a subscription plan for Jira Cloud only. Jira Premium does not apply to a Jira Server…
-
What do you mean by "share"? Having Company Managed (previously known as Classic) projects and Team Managed (previously known as Next Gen) projects in one Jira instance is possible only when you are using Jira Cloud. If you are talking about the Dashboards that are created from the Dashboards menu option in the menu bar at…
-
What do you mean by "work with it"? As Jack said, Jira Premium is a Cloud solution. Standard and Premium are the subscriptions plans that you can purchase for Jira Cloud. That would be an entirely separate Jira instance from your self-hosted Jira Server instance.
-
Can you clarify what you mean by "migrate"? Dashboards are typically comprised of gadgets that reference projects or filters to determine the data they present. You can change the configuration of the gadgets to reference different filters or projects. If that doesn't address your question, please provide more details…
-
I posted a response in your first post - is this really about a Jira server instance or are you asking about Team Managed project in Jira Cloud? Can you provide more clarity on the filters about which you are asking? It is possible to create your own filters for searching for issues in Team Managed projects just like you…
-
You have tagged your post as 'jira-software-server'. Are you asking about next-gen projects (now called Team Managed projects) for Jira server or Jira cloud?
-
Jumping in rather than starting a separate response thread. If you are able to get a report of the issues the includes the name of the person to whom you want to re-assign the issues, then one way you could execute a bulk change would be to 1. organize the list by the person to whom you want to reassign the tickets 2. In…
-
Hello @Esther Lu Welcome to the community. Are your projects that contain these issues Company Managed projects or Team Managed projects? It will say in at the bottom of the navigation pane on the left. If you are working with Team Managed projects, you cannot have Epics and their child Stories in separate projects. They…
-
Per the documentation you need to include the fields Start Date and Due Date in the issue types and set the values for them.
-
Hello anna.burger@twofour.de You cannot do that with the native functionality for creating a Company Managed project. Company Managed projects can have multiple boards associated to them, so there is no way for the native project creation functionality to know which board would need to be copied. There might be a third…
-
First, some background. Issues exist in a project, and an agile "board" is a method to manipulate those issue following an agile methodology (scrum or kanban). The agile board is the resource that holds the board view of cards and the configuration of that board, the backlog, and, in the case of scrum, the sprints. Board,…
-
So, it is not the searching/jql that is the issue. Rather, the issue is that you are using List View for the output and wanting to include the Parent field in the columns of output in List View? That is a puzzler. I work in Jira Cloud, and I can see Parent as an option when I am configuring the columns of the output…
-
Jumping over to this thread from my original response because what you've posted here now gives me clarity into your situation. The "wrapping" that you are seeing is based on the parent/child relationship of the issues. When an issues parent is recorded in the field named Parent, then you see the wrapping behavior. For…
-
This is not the same in Jira Cloud for Team Managed projects. Jira Server is similar to Jira Cloud Company Managed projects. but Team Managed projects have a very different workflow management process.