Nic Brough -Adaptavist- Expert

It's only for issues that are "done" - they are in the last column on the board. Other issues, by definition, are not done, so they will never be hidden.

As I said in my original answer, there are no priority schemes on Cloud yet. You can only do this with a custom field as Perisic said.

Welcome to the Atlassian Community! The numbers displayed in the config screen are simple counts of issues currently in the status the column is mapping. They're not showing you what the board is actually going to display. You need to look at the board filter to see what the board should be showing, and check that all the…

See https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/

Custom fields can be limited to projects, so if you create a custom field for your priority, yes, you can choose to use it in only one project.

Welcome to the Atlassian Community! You will need to talk to your organisations administrators. The Atlassian Community can only help you with questions about using Atlassian software.

Welcome to the Atlassian Community! Talk to your administrators, they can edit the workflows and add the status for you.

Hi Kimberly, On cloud, no, but you will be able to soon. https://jira.atlassian.com/browse/JRACLOUD-3821 is in "early access", so some people can have priority schemes, and there's a 99.9% chance that it will be rolled out to everyone very soon. (On server/DC, we've had priority schemes for years)

Welcome to the Atlassian Community! You will need to tell your administrators to let you have access to the log. The only way you can debug this problem is by reading the logs.

Could you show us a filter result that shows issues that have values for the fields showing as 0 in the widget?

@Daniel Howard Welcome to the Atlassian Community! I don't think you've quite grasped the argument here, a lot of what you have written is right, but you contradict yourself partway through it and get a bit lost in the middle. >> If your "User Stories" are to actually fit the Scrum model, they must include all the elements…

Why would it need to be? The marketing and documentation all make it perfectly clear what Bitbucket does.

Remove the quotes from around cField. You are passing in cField as a string, which won't work. cField is supposed to be a custom field object, as defined in Mark's code in the "def cField = ..." line.

Hi Monica, I can not see a way to do this on Cloud or DC with Scriptrunner. This is because you can't do it in Jira. There's no way to inject anything into the "create version" (or "release version") process, you would need to amend the screens at the beginning of the process to enable them to validate what was being put…

I am sorry, but Jira doesn't do the (customized order of the components) bit.

In the background, there's a table that keeps a pair of values when you move an issue. Very simple, two columns of issue-key and issue-id. The issue-id is the id in the database and it never changes. But evven if you move an issue several times, it keeps a record. This means the quick-search can understand that what was…

Welcome to the Atlassian Community! You don't create any end-point in Jira. They already exist automatically. To "get" the endpoint you want to use, you will need to read the documentation over at https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ to work out what the end-point you want to hit is, and then…

Welcome to the Atlassian Community! Neither "wins". Atlassian systems have a simple permissive model (although there are ways to do individual restrictions at an item level). If you give people admin, they can do admin things. But just admin, until you let them in as something else as well. A project lead with Admin and…

Jira can do it, but it won't be Scrum or Kanban, it will not be pretty, and you're going to have massive problems doing it and reporting on it. I'm afraid your process is broken.

Um, "With the custom fields, whether provided by apps, or the Jira platform, you have a simple list - go to admin -> issues -> custom fields."

Atlassian can't code for that. Your filter or project usually won't name the field you want to run the pie-chart against. For example, a filter for "Project = X and component in (a, b, c)" does not name the assignee which is what I want to use as the statistic type.

Welcome to the Atlassian Community! The best way to manage an issue that has to go through multiple sprints is to not do it that way. An issue should be completed within a single sprint. If you think you have issues that will need to be done across many sprints, then you are not devolving your stories enough. The whole…

Welcome to the Atlassian Community! * Boards only belong to projects if the project is team-managed, or not Software projects. You can not have multiple project boards, but you can create many boards in Software projects * Yes, you can do this with issue security, but only in company-managed projects (team-managed projects…

Welcome to the Atlassian Community! You can use validators to do this, but you will need to find an app that provides a validator for "number is larger/smaller than", the built-in ones do not have that

Hi Mouna, What type of field is "issue age" and how is it being set?

Hi, Jira does the right thing with the assignee, it only lets you set it to the one single person who is currently responsible for dealing with the issue. You can not set groups or multiple assignees (because that's a dreadful thing to do) You will need to create a new field for multiple "people to talk to if the owner…

I am not sure that I understand the question, but I can say that Atlassian will be supporting all the migration tools for moving from Server or DC to Cloud for a long time/

Welcome to the Atlassian Community! Short answer: No DC is here to stay. DC clients are large (the minimum size is 500 users), and there are a lot of places that can never go to the Cloud. I have more than 50 customers who will never move their DC data to cloud, and some of them are constrained by law - it would be…

You say "created a new filter", but you do not say that you changed the board filter to that filter (which you can only do for Jira Software boards that are based on a filter - you can't do that on project boards like the ones provided by team-managed projects)

Welcome to the Atlassian Community! I suspect your board's filter includes a range of projects, some of which are team-managed. You can duplicate status names in team-managed projects, so I think your multiple done/to-do/in-review are coming from the different projects.