Trudy P Claspill Community Champion

@Balaji Mohanraj That is just simply how Jira works. It appears that for the Sprint field, in the Basic search functionality, the list will display only 5 matches and tell you that there are more potential matches.

I think this post might help you solve your problem. https://community.atlassian.com/t5/Jira-questions/automation-Advanced-compare-quot-or-quot-condition/qaq-p/1815711 Or you could try using the contains regular expression comparison

My apologies. Are you planning to upgrade an existing Server with a Data Center license? Or are you moving data from a Server instance to a new Data Center Instance? Here are two documents that will help you get started:…

Hello @Michael Martin Welcome to the Atlassian community! In addition to what the others have said 2a. If you enabled Anonymous access, that would enable no-charge access for any user on the internet who had your Confluence URL. 2b. With the Premium plan you can enable Anonymous access and use IP/CIDR white listing to…

The Confluence guest user beta mentioned by Jens.

Hello @Nik Jordanov Welcome to the Atlassian community! There are two pre-built fields for story points: Story Points is a custom field that is available for Company Managed projects. Story point estimate is the equivalent field, but used only in Team Managed projects. Natively Jira does provide two story point fields…

No, not for a Team Managed project issue. I worked on it a few days ago and could not find the right value to use in the JSON code that would result in clearing the field. I tried "" null 0 "0"

Hello @Shikha Verma You need to remove the curly braces around Cancel in that comparison. The curly braces tell the Automation rule that is a smart value. If you want to see if the comment body contains the literal text Cancel then remove the curly braces.

It is part of the Edit Issue action in an Automation Rule.

Hello @Thays_Carvalho If you are using default configurations for your projects and subtask issues types this is expected. Story points should be used to estimate at the base issue level, not the subtask level. At the subtask level people more often use time in Original Estimate for estimation. You can, however, modify the…

Hello @Philip Marvil For Company Managed projects the configurations are managed by Schemes that are associated to the projects. A single Scheme may be used by multiple projects. To confirm that only your one project is affected, the Jira Administrator will have to ensure that it uses certain Schemes that are used only by…

Hello @Carolina Chavarria Welcome to the Atlassian community! Yes! You can use the Automation for Jira feature to automatically create an issue in a Software project based on activity in an issue in a Service project. The home page for Automation documentation can be found here:…

Hello @Sierra Are you talking about making an additional Kanban board for an existing project, or are you talking about selecting the option to create a Kanban board at the same time you create the project? A Kanban board is just a way to view and manipulate issues in a project, selecting the relevant issues based on a…

In the first screen image you provided you can see that a Screen has been attached to the Transition. Regarding the Resolved date/time field it is displayed automatically for all issues that have the Resolution field set.

Hello @Chris Gunnels Welcome to the Atlassian community! For Business projects Jira does not automatically set up the workflow to set the Resolution field. This is noted here: https://jira.atlassian.com/browse/JWMCLOUD-180 For Team Managed project currently you can't set/clear the Resolution field through workflow…

Привет @688-685 , Добро пожаловать в сообщество Atlassian! Какое сообщение об ошибке вы получаете, когда пытаетесь получить доступ к этой ссылке? Обратите внимание, что мы в этом сообществе являемся пользователями наших собственных экземпляров Jira. Мы не являемся администраторами вашего экземпляра Jira и не имеем доступа…

The challenge you will face with that solution is that Team Managed projects are all intended to be independently configured by their Project Managers. They don't share configuration elements (all though there has been a recent change to allow them to share fields). When you clone those Team Managed project issues into…

That is really odd. When you click on the + field in List View, does it show you a list of fields with check marks next to the ones that are already displayed? Do you find Category if you just scroll through the list?

Hello @RG Atlassian has provided a great deal of information on this topic. Here is a starting point with links to other resources. https://www.atlassian.com/migration/plan/cloud-guide

What type of projects are you working with? Team Managed or Company Managed or both? Software, Service, Work Management, or a combination? Depending on your answer, one solution could be to create a project for the separate leadership issues, and then simply create a Board that combines issues from all the projects into…

Hello Tamara, Thank you for that additional information. In that case you would want the Link Type selected in the second step to be "clones", not "is cloned by".

Hello @Remya Ramakrishnan Welcome to the Atlassian community! That is not how plan licensing is applied. Your entire instance is assigned a plan type - Free, Standard, Premium, or Enterprise. That plan dictates what functionality is available on the instance. All users are billed at the rate for the plan type for the…

Hello @Sam Reilly Welcome to the Atlassian community! Can you provide more information about why you want to duplicate the issues into another project? You indicate that you would want them to stay synchronized with the original issues. What do you want to do with those copies of the issues that you can't do with the…

The fact is that if I remove some columns, that leaves some status "unmapped", and if I switch to the backlog view, I can't see anymore the "unmapped" statuses. Yes, that is the way the product is designed to work. The Backlog and the Board view are based on one filter. Besides the alternative of creating another board…

Hello @v01dv01d Welcome to the Atlassian community! It is not possible to hide a column on the Scrum board. You can hide issues on the board, but not a column. You could construct a second board that pulls in the same issues, but change the column configuration so that column is not present. Can you provide screen images…

Hello @Dom Bush Given that the projects are Team Managed, for the one where the field is not available for you to add to the List view can you navigate to Project Settings > Issue Types and show us a screen image of one of the issue types showing that the Category field is included for that issue type?

¿Puede ir al Editor de flujo de trabajo, ir a la pestaña Validadores para una transición de flujo de trabajo, comenzar a agregar un nuevo Validador y mostrarme la opción de Validador que está eligiendo cuando agrega un Validador como los del flujo de trabajo actual? --- Can you go to the Workflow Editor, go to the…

The image you provided appears to be for a workflow. The BACKLOG status shows "<-- ALL". That means an issue in any other valid status is allowed to be changed to the Backlog status. There could be Conditions or Validators associated with the transition to Backlog that could prevent that transition from being available or…

It is hard to answer your question based on the limited information available. Most of the bullet items you listed can be satisfied by Jira Work management, and based on the working pattern you initially outlined. However, some of the items in your bullet list need more definition for us to understand what requirement they…

I don't see anything obviously wrong with your filter but there are two changes I would recommend. 1. You don't have to list all the Epic Link values separately with OR's. Instead use "Epic Link" in (<comma separated list of the Epic issue keys>) 2. When creating a filter for an agile board the ORDER BY clause typically…