Nic Brough -Adaptavist- Expert

You've said Cloud in your question, but you've been reading a guide for Server/DC. For a change, this doesn't actually matter, as the principles might be the same. On Cloud, we can create team-managed (next-gen) or company-managed (classic) projects. Server/DC only really has company-managed projects, and they're pretty…

Probably the easiest way is to use the call to "get all issues for a sprint" ( https://docs.atlassian.com/jira-software/REST/7.3.1/#agile/1.0/sprint-getIssuesForSprint ), then read each one of them for their estimates and status at the time the sprint ended if it's not the current one. (You may need to read the board…

Your Jira server is connected to a database that is not responding to it any more. Possibly a network error (unlikely given it says "localhost"), but most likely simply that the database service is not running any more. You will need to restart the database service (or restore the network connection) and restart your Jira…

Either you have sub-tasks enabled, or you do not. You can't hide the create option arbitrarily, Jira can't know when you think it's valid or not (and doesn't support it anyway)

I'm not sure what else I can tell you. If your server cannot look up and talk to the marketplace server over its network connection, then it's either the connection settings, or a firewall blocking access to that part of the internet

If no projects or issues appear for you, then it's likely that you have not got permission to see them. Check the project settings (as an admin, you should be able to get into the admin for projects, even the ones you can't see) - look at the users and roles if the projects are team-managed, and the permissions…

Sorry, I wasn't giving you JQL, just the principles. Yes, I would use closedSprints() to do the "issue is in previous sprint" part.

On Cloud, there's only one way to control cloning - you can flag a step in a workflow with "jira.permission.create.clone = denied" - this will stop everyone having the clone function when an issue is at a particular place in its workflow (you can, of course, add it to every step, which would disable clone completely for…

The Sprint "field" on an issue retains all the active sprints an issue goes into, so you could look at "Issue is in current sprint AND issue is in previous sprint"

How are you telling Jira that a project is "done"?

I'd say it's because the server can't reach the marketplace to do the upgrade.

What fields are missing?

There are two reasons this might happen. First, the Service Desk application version might not be flagged as valid for your current version of Jira. In this case, there's nothing you can or should do. Second, your server may not be able to reach the marketplace site to check the versions, so it doesn't know that there is…

It will vanish if you remove all the sub-task types from the project's issue type scheme.

Have you put data into the fields? Jira doesn't display empty fields.

There are loads of samples out there, it's more about finding one that works for you than finding any. Although generally, the REST API is relatively easy to use and it's harder to work out how to use a library than it is to just do the calls directly yourself. All of them are, of course, based on using the REST API -…

Right, so your create issue screen does not have the assignee field on it. You'll need to add that, or make it optional in the field configuration

It looks like you have not added a field for "end date". To the right hand side of your screenshot, there is a section that allows you to add fields, you can add it from there

It's under manage apps -> app -> configuration

Your process is broken, you're not doing Scrum. Change it so that you are, and you have a useful definition of done, and the sprint report will start working.

Khoros (the platform running the community) is not an Atlassian product. They have developers working on it, but this is just for Atlassian community customisation and experience. A mobile app is something Khoros should be responsible for, not Atlassian!

We can't. You can though, go to https://id.atlassian.com/manage-profile/account-preferences and click delete account, it will walk you through it.

Just not a lot of call for it, so it's stayed low on the list.

Not without coding for a web-fragment.

Jira Cloud does not yet support the functions that Scriptrunner on Server does that could help you with this (Behaviours). As you suspect, the listener is too late - the create event is fired when the human clicks the "create" button and commits the data they've entered (including description). Your script, if run as a…

First, log into admin.atlassian.com with the account you are using here. Just to check what you can and cannot do with it. Next, is to raise a support request (with the account you are using here) over at https://support.atlassian.com/contact/ explaining the problem, and giving the url to your Cloud system plus something…

Yep, Epics are a bit of a botch in Jira Software, even to the point where they have the wrong name! (Still, at least they got rid of the utterly hideous botch of Greenhopper abusing resolution to represent status, those were dark times)

I'd recommend that you share workflows as much as you possibly can. This helps people work in similar ways across teams, keeps administration simple and enables you to report consistently across teams (in a lot of cases, where people have diverged on their workflows, cross-team reporting becomes impossible) Imagine trying…

Ok, there's some confusion here that needs clearing up. Epic Status is NOT the same as workflow status. * Workflow status is not a field, it is an indicator of where an issue is in the workflow * Epic Status is a field created by Jira Software to represent the broad status of an Epic. Epic status is independent of the…

1. Could you show us what you have configured for the schedule? 2. Edit the workflow, you can change the "create" transition so that it lands on another step.