Nic Brough -Adaptavist- Expert

That's fine, you just need to fix your board definition. Map both "Story Done" and "Done" into the last column on the board. However, in the other thread, you actually state that you've created another problem. You can't use two separate boards like that. A sprint looks to the board it belongs to for the last column. Your…

See https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ You're probably looking for jira.permission.comment

1. You look at the list of issues, the highest ranked one is at the top, the lowest at the bottom, and the others in order between those two 2. Yes, rank is a unique value across the whole system, no two issues can have the same rank 3. Status change does not change a rank, unless it is something that moves an issue into…

There's three things wrong with your JQL: "jql": "project~Teste AND summary~second Rest Issue", * You need spaces to delimit fields and operators in JQL * You need quotes around strings if they have spaces in them * The project "field" is a select field, not text, you can't use the fuzzy operator search (~) Try:…

Welcome to the Community! An issue is only "done" when it is in a status that is in the last column on the board. My guess is that your stories have a "done" status that is in the last column, but the "done" status for sub-tasks are not mapped into the last column, so the issues are not done as far as the Sprint is…

That's not how it works. There is no "automatically receive a licence", as the licence is a single licence that applies to your server, there is nothing given to a user. There is nothing here to "disable", there's nothing actually being done. Your licence says "you can have up to X users able to log in to this system". The…

This is down to the context of the field, so you probably need to check the context again - are you sure it is set for the project and issue type? You need to check that for all project and issue types that your search might return, not just the issues it currently does. If you have changed the context for the field, did…

No, I'm afraid the display of the status is fixed to outline/colour like this on Cloud

Ok, I suspect you have created "documentation" as a sub-task type. These can't appear on the "create" drop-down, you can only create a sub-task from the issue that it will be a part of.

I am really sorry, I do not understand "documentation shows as a new scheme"? Maybe try a different order - go to the project you want the new issue type in, go to project settings and find issue types. Select edit to go into editing the scheme and you'll find you can add/remove issue types from the global list and create…

Ok, so where are you stuck on creating a new issue type and adding it into your project's "issue type scheme"?

What type of field did you use exactly?

Ok, so, briefly: * Add the custom fields you need to the system * Set up the "create issue" screen for the project and issue-type such that it includes all the fields you need on the form And that's about it! There's no real difference between a JWM and JS screen - that's the way you set up any "create issue form"

The history is not a field, it's not exportable. With the REST API, it's not something you build, it's the remote interface built into Jira - you would write code to interact with it over the network. Start with a browse of https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Your project is a team-managed project, which do not use schemes for their configuration. You configure the issue types directly in TM projects in the bar on the left hand side of your screenshot.

You'll want to be reading the issue history. To do that "in the UI", you would simply visit the issue in a browser and read the history. If you want to get it out as raw data, you probably do want to read the issues over the REST API - that can return multiple issues with any/all the data on them, in a machine-readable…

Not really. The "work management form" is a create screen for a project and issue type. Jira Software works the same way. (Jira Service Management also does issue create, but additionally has requests, which go in front of the issue for customers and are a simplified view) As an example, I can go into the acl-sandbox Jira,…

Welcome to the community! You do not, the time-remaining is part of the time-tracking field, not an independent thing. You could copy it out to a scripted field, but that's clunky and would require maintenance, plus explaining to people why you've got it in two places!

What exactly did you back up and restore when you "regressed"? Jira doesn't have a downgrade process, you have to roll back to a backup really, if you've not just thrown away all of the upgraded system and gone back to the 8.4 entirely, you may have left 8.20 files all over the place which could easily break when you try…

What do you mean by "intake form"? The create issue functions in Jira Software and Jira Work Management are similarly configurable, and you can make them work pretty much identically if you want.

What do you mean by "outline"? I've heard different people use it to describe different things. The one I'd usually head for in Confluence is a "table of contents" - there's a simple macro in there that reads the headings in a page and turns them into a table of content, indented by level of heading. You can configure it…

This is one of the reasons that you should stop reading the database - it is not designed or intended for reporting and is hence an utterly dreadful thing to do. Use the REST API instead, it's faster, easier and will give you the results you need without having to mess with understanding the database. If you insist on…

Welcome to the community! No, because they're not burn-downs. You burn down an issue's estimate when the issue is done, not at other points in its life-cycle. You would also have a problem with the lines in that they would go back up as the issue moves - that would really never make it look like a burn-down at all. What…

Your app may have used features in Java that are used slightly differently in the new implementation. I've seen this happen with different versions of oracle java and when running the same version of it on Windows and Linux, so it might not be the swap of JDK. The solution in my case was a slight change in the version of…

Welcome to the community! I'm not sure what you mean by "enable", as the REST API is always available, there's nothing to "enable" I think a walkthrough is the best way to go here, because although the docs are littered with examples we could point you to, they're written more as reference guides for people who already…

This sounds like you do not have a premium (or enterprise) subscription to Jira! IP Whitelisting is only available to premium.

That's quite a hard calculation to make (assuming by "volume consumption", you mean "disk space") Imagine the simple case: Bob creates a page, which has a few paragraphs of text on it, and adds an image (as an attachment). You now have to count two things - there's a set of lines in your database containing the pages…

Welcome to the community! "did not have a whole lot of success" does not help us understand the problem. Where exactly are you stuck on this? Are you definitely in a company-managed project? Or are you stuck on creating the issue-type scheme? Or getting errors when editing it? Or something else?

I've seen a workflow change corrupt a project once (For background, I've been here a while - started with Jira 2 around 16-17 years ago). The migration failed part way through (actually, someone stopped the server part way through. I should have checked which system I was looking at!) and the only bit that went wrong was…

It won't. Atlassian don't look to Community for helping rank their backlogs. They do look at votes on issues in their Jira (and they do take items from Community into it) See https://jira.atlassian.com/browse