Nic Brough -Adaptavist- Expert

Ok, your URL is for a Server/DC install, not Atlassian Cloud (they all end .atlassian.net for now - there's a long-running jok^H^H^H request out there to allow custom domains). Trudy is exactly right about contacting your admins, it is your only option, but there are three possibilities behind the missing workflow items…

This is definitely one that needs to go to Atlassian! Jira Service Management's model of the helpdesk expects a very high ratio of customers and developers to Agents, they're simply not expecting anyone to need 5000 agents. But we can ask! Out of curiosity, what is your model that means you need that many Agents?

It's more of a migration than an upgrade, but it is quite simple compared with a big upgrade or moving to Cloud It's more complex than this, but the bigger steps are: * Build your new DC install (even if it's just a single node to begin with), with the shared storage and database backend you want * Install Confluence 7.13…

Welcome to the Atlassian Community! I suspect you have let people create "team managed projects" - these don't use the global list of status for their workflows, they use their own local lists which can then duplicate status. The search options can only present you with a list of all status in the system global and all the…

Welcome to the Atlassian Community! I think you may be in the wrong place. I think the system you are asking about has its documentation hosted in Confluence, and you have clicked on "help with Confluence", rather than "help with our application"

I don't know! If the browser can render it, it must be a bug in Outlook.

I know this is not an answer to your question, but I need to question why you are doing this. Are you using "Estimated Story Points" as your board estimation statistic?

Jira uses "issue" to mean "item that needs some attention", and it uses it everywhere. You really don't want to change it to "ticket". It's a bad word to use to describe issues (issues isn't great, but ticket is just plain wrong. Bugs, Tasks, Epics, Defects, Meetings, etc, all could be described as "issues", but not…

Ok, so it's not really a "parent" you're trying to create. You can set up an automation that creates a new issue when any issue goes through a specific transition, and set a link on the new issue back to the "trigger" issue while you do it.

Bother, I forgot. If you genuinely want to dump the backlog ranking functions, and treat it as though it is a queue, then it's actually quite simple. Change the board filter from ending with "Order by rank" to "order by priority, release, epic-link". There's no need to run a sort that way, it'll always be in the right…

I'm afraid the way Qase works means that you have to have that administrative user. You will have to add one.

The main one for me is that Jira Scrum boards are built to support Scrum and only Scrum. If you're doing Scrum by the book, then Jira works great, and it supports most of the variations you see within it (estimates on any numbers you want, more rigid workflows than "can move it anywhere I feel like", breaking stories into…

Welcome to the Atlassian Community! You would need to build a REST API script that re-ranks your backlog in batches of 50, via https://developer.atlassian.com/cloud/jira/software/rest/api-group-issue/#api-rest-agile-1-0-issue-rank-put I would very strongly recommend that you never do this. You are destroying the ranking…

You will need to use one of the apps that helps with reporting or migrations, most of them can list out filters. Or you can scrape them over the REST API.

Not on Cloud you can't

Welcome to the Atlassian Community! The problem here is the mixing of AND and OR to join the clauses. When you do that, you have to tell Jira exactly what you mean, otherwise it has no choice but to read left to right. In this case, you've told Jira to produce a list of issues that match either of these two queries: *…

There is no way to do that directly on the status, you'll need to do some coding. The way permissions work is that someone with "assign" can assign an issue to anyone who is "assignable". You can't vary the "assignable" permission based on who the current user is. You can however prevent issues being moved through the…

What type of field is "customer name"? Can you go to Admin -> Issues -> Custom fields, find customer name and look underneath its name for the type?

Welcome to the Atlassian Community! This should be just text ~ "change request related to metadata and reporting properly routed via business data steward using Jira"

Oh, absolutely. Splitting it into a dev story and a test story is a blunt and simple approach that kludges past this problem. Splitting the story up into several deliverable stories is by far the beter thing to do.

Those functions can be very slow, especially when you're working with a large data set, and looking for data that is not indexed (in this case, the board relationship with an issue is not indexed, so you're making Jira work hard to look it up) I would change the query completely. The results you should get from the query…

Or get yourself added to one of the groups that has "create space" permission - you don't have to be a full admin.

A link to what? I can't tell you where your Jira is! But, it's not hard. Log into your Jira, click on "dashboards" in the main menu, and select "create dashboard". Name it, choose who you want to be able to see it, and then start adding the personal stuff you want to it.

You might not have changed anything, but the message is clear - you've left fields empty and the system is configured to require them. The last time it worked, either you entered data into those fields, or your administrators changed the validation since then. 

No. But you can create a personal dashboard. Everything within a personal dashboard is up to the owner to define and own then.

You need to add the *24 to each of the three calculations on the fields, not the overall result.

Welcome to the Atlassian Community! The proper way to do this is to split the story into two or more stories that can be completed within a sprint, exactly as you say.

You can't at the moment. As I said, Atlassian restricted the use of them to people who had already enabled them.

You can't do it (without looking at permission schemes)

This is because the script does not go through the workflow migration process for existing projects. It's basically breaking things and you shouldn't be using it to change schemes (for any projects that have existing issues)