Trudy P Claspill Community Champion

Ok, so when you say you want issues where the "Confluence Quality" field has "any gap", the options for that field that represent "gaps" is only a subset of all possible options on the field. Since my logic was otherwise correct, I recommend that you update the JQL as shown below, repositioning the Ticket Created criteria…

The functionality may have changed since last I used it. As I recall we used the tombstone option only on users that did not already exist in Cloud. We specifically used it when we did not want a user in the on-premise instance to have a corresponding Cloud account created as part of the migration.

https://jira.atlassian.com/browse/JRACLOUD-87945 https://jira.atlassian.com/browse/JRACLOUD-86363

Hello @Johel Ascona Welcome to the Atlassian community. Jira natively does not provide the capability to search for issues based on a comment having been made by a specific user on a specific date. Are you open to getting a third party app to meet your requirement?

Given that no other responses have appeared here, I recommend that you open a support ticket directly with Atlassian. https://support.atlassian.com/contact/#/ It would be great if you could share here what you learn from Atlassian about the root cause and fix.

Adding to what the others have said I want to call out a risk. If you already have Spike type issues, and if they already have Child issue associated to them, then moving the Spike issue type to another level will remove the connections between all Spike issues types and their Child issues.

If the workaround ends up working for you, at that time please consider clicking on the Accept Answer button above my responses to mark your Question as Solved. If you need additional help on this, don't hesitate to ask.

Olá @Vinícius Pereira , A resposta curta é que não existe um recurso automatizado para gerar Raias com base nos níveis de hierarquia acima do Nível 1 (Épicos). Você precisaria usar as opções de Consulta para raias e criar uma JQL explícita para cada Iniciativa para definir cada raia. Ainda não encontrei uma solicitação de…

If you are working with a Team Managed project, then go to Project Settings for that project. Expand the Work Types section and select the work item type for which you want to set default test in the Description field. In the center panel the fields shown for that work type will display. Expand the Description field by…

I'm not able to think of anything else that might cause this. I have flagged your post to raise it to the attention of Atlassian Team members. They should get back to your within 2 business days. It would be great if, after discussing the problem with them, you report back here what you learn.

@Prachi Bolar The tags on the post indicate the author is using a Free subscription. Users of Free subscriptions are not able to create support cases at https://support.atlassian.com . They get redirected to asking for help here in the Community Forums. However, for Community Champions and others (I assume Atlassian Team…

Hello @Abdullah Alquraan Do you have the same issue regardless of the issue type you try to create, or the project in which you try to create it? Do other users of your Jira instance experience the same problem? Have you ever been able to create issues successfully? How long have you been experiencing the problem? Another…

Hello @gomathi gunasekaran Welcome to the Atlassian community. You can see information a user's profile by navigating to the Teams menu and searching for the user. When they are returned, click on their name in the results to see the details of their profile. You should be able to see their email there if you have the…

Hello @Asel Turgunova Welcome to the Atlassian community. What types of projects are you creating? Get that information from the View All Projects page under the Projects menu, looking at the information in the Type column. For Team Managed projects the Access settings of the Project may default to Open, which would enable…

Can you check the mapping of Statuses to columns for your board and confirm that the Statuses used by the Epics are mapped to board columns? Click on the ... button on to the right and slightly above the columns when viewing your board, and select Configure Board. That should give you a screen that looks similar to this.…

@Alyssa Coke Were you able to find the root cause of your issue? If so, can you share the details with us?

Actually, the documentation for Managing Filters makes it should like using the Share button should work. https://support.atlassian.com/jira-software-cloud/docs/manage-filters/#Share-a-filter

I'm glad you discovered the solution. That option is a different type of sharing. That is simply sending a message to the specified user with a link to the filter. It does not actually give them permission to access the filter. I'm still looking for the documentation that actually describes that button. It is a bit…

I did not phrase that question properly, I think. Do you have any third party apps that extend the capabilities of issue searching (i.e add more options to use in JQL) in Jira? The Rich Filters app does not appear to help in that regard, though I am not well versed in that specific app. JQL Search Extensions, for example,…

Hello @Leo White Were you able to solve the problem by adding yourself to the Administrator role of the project? Or did you find another way to solve the problem? Or did it remain unsolved?

Hello @Jeremiah I see that also. I recommend that you use the Feedback option under the Help button (next to your avatar) in Jira to provide that feedback directly to Atlassian.

Hello @Rashmi Advani Welcome to the Atlassian community. Can you confirm you are working with the Jira Cloud product vs. Jira Data Center? What is the type of the project you are using? Get that information from the Type column on the View All Projects page under the Projects menu. If you are working with Cloud and are…

Hello @Ollie Otulakowski Welcome to the Atlassian community. Do other users encounter the same problem in the same project? Are you able to create issues in other projects? Have you tried the same actions in another browser app, or after clearing your browser cache, or in a private browser window (to determine if the issue…

Hello @Stephen Chisholm Releases is now a tab that appears among the tabs across the top area of the page. The order of the tabs may be different for you.

I think I was not clear on what I was suggesting, which is that you would change just the portion of your JQL referencing the "confluence quality[dropdown]" field. You still need the rest of the JQL statement. I'm also not sure I understand exactly what you are trying to retrieve in this statement because of your…

You can use the following API end point, supplying the numeric ID of the sprint, and get the numeric ID of the board in which it was created. https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-get You can get the numeric ID of the sprint by starting with a JQL…

So, the work item moves to "Test" when dev is done, and doesn't move to "done" until it is deployed? And you can't tell if testing is actually completed or in progress or not started? What I'd like is to have a system where once dev is done, it's done. I would ask you to consider carefully what the root problem is that you…

Hello @shobana.sathyamurthy Were you able to achieve your requirement with the information I provided? If so, please consider clicking the Accept Answer button to mark your Question as Solved.

Hello @Kalin Taylor Were you able to get the assistance you needed from the app vendor? Can you share with us anything you learned from them, in case somebody else with the same issue searches this community for an answer?

Thank you for that additional information. I still need some clarity on the separation of Dev and QA work. I'm not sure if I'm asking the question clearly. Does the work item remain "incomplete" at the end of the Dev sprint (Sprint Burndown does not burn down the work items as Dev work is finished) and move into the next…