Nic Brough -Adaptavist- Expert

Atlassian are looking into this, we've given them several examples of answers going missing.

You won't really be able to notice a difference, but putting individual users in is actually slightly faster than groups. The permission check takes the current user and says "can this person do this". If you use users direct, the check comes back with an answer. If you use groups, the system has do check what groups the…

Jira does not have anything to "constrain" an app. You can only do it if the app provides some form of access control (and limiting use will not affect your costs, if that's why you're trying to do it)

The number of projects you have is not much of a concern when it comes to the performance of boards. The volume of issues in a project is similarly unimportant. Yes, if you have a lot of projects and issues, there are load-generating consequences, but Jira can work fine with millions of issues across thousands of projects,…

No. That's not how permissions work. This is a deliberate design choice, permissions are not something you want to have a free-for-all on, they're already complicated, this would be a terrible appraoch to it

"Administration" as in system administration, not project. See Janet Albion's answer for the field name.

Atlassian are not a credit card company. I think you have a credit card company that uses Atlassian for some of their documentation and you have followed a link for help with that system, rather than a link for help with their product? If you do mean to be talking about Atlassian, we'll need a lot more information - how…

Yes, it's gone, but you can use / instead

You don't need to add epic link in NextGen, it's done by using "add parent" on the story.

My guess is that all your issues have one or more labels. Try: fixversion in ("Blue Button Prototype", "EPM Upgrade Planning (Tech Roadmap 2021)", "InCommon for ECHO", "Cloud Implementation 1.0", "TrialPay Replacement") AND (labels not in (FY21TechRoadmap) OR labels is empty)

You can upgrade to any version that was released before the expiry date of your current licence. You can work that out from the dates on releases when you go to download Confluence and by looking at your licence. For what it's worth, only ast week I moved from a 5.0 to a 7.4 release - there were very few apps installed,…

You can only estimate on one statistic. You need to decide whether you're going to use your rough estimate or the time-tracking consistently.

No, there's no way to do this. If someone can add a custom field, they can set any context and it defaults to global.

What field? 

What is the field that is doing this? Assignee, reporter, something else?

This can't be done - a template is, well, a template. It's used to create a page. It's nothing to do with the page once you've used it. (Imagine you're using a "cookie cutter" to make shapes in food - once you've shaped the food, does it change shape because you buy a new cookie cutter, or drop the existing one and bend…

In the project settings, you can add fields to the project.

I suspect you might find it's the number of issues you have on the board. Until Jira 8, we'd recommend you draw less than 250 into a board, as you started to see significant pain when there's more than 300. Jira 8 improved it on Server/DC, but I don't know if any of those improvements were done on Cloud. I've jumped on…

Code. The screens and fields are coded differently. In fact, there are only two functional types of screen in Jira - view and edit. The create screen is simply an edit-type screen that is displayed at create time. Code does all the rendering, and where the screen is in use is what determines how it grabs fields. Fields…

Argh, sorry, I forgot - you'll also want to copy the plugins directory, otherwise you'll need to re-install the plugins after migration.

Yep, plus the xml you took for the migration.

You know they get added back when the issue is re-indexed?

Filters and dashboards are part of the reporting. People can create them when building their own reports, and then choose to share them with other people, so people are reporting on the same things. The setting in your screenshot is about to whom a filter or dashboard is shared by default. The inherit thing is what it says…

Start by establishing what is slow and what the load patterns are. * Monitor the server - are the memory, cpu, disk io, database, proxy and/or network significantly loaded? And by what? * What is the latency between your client machines and the AWS system? (For example, are you in say Europe and the AWS service in North…

You've only given us the middle part of the error. The beginning and end are more useful in debugging - what was the first part of the error that lead to the "at" at the top of your snippet and what are the "caused by" errors after it?

I do not think I understand the question. But if I take a bit of a guess, it is that your client has a broken requirement and is trying to use Jira as though it's one of the legacy systems they have moved away from. The summary field is for a quick short human-friendly bit of text that acts mainly as a natural language…

Without any context of where you are seeing these, or why you're asking, all we can do is guess. Filters and Dashboards are things for giving information to users. They're one of the the reporting systems in Jira Inherit from global settings is found in a few places where you can localise settings, but you may want to…

Standard advice: * Do not touch a Jira database. Unless you have a complete understanding of how the parts you want to change work, you will break your Jira. * You must never touch a Jira database while Jira is running. With some trivial exceptions updating non-issue data, you will break your Jira. * If you must edit a…

Three options, depending on what you really need, as I'm not 100% sure from your question. Is it a blanket "no-one can go from in-progress, in review or done, back into to-do"? If so, then just delete the "all" transition Should there be only one or two places? For example "you can go back to todo from in-progress, but not…

@Jimmy Seddonyep, we've used it a couple of times now. Not a "convert production" as simply as I said there, but not far off - a flat copy of production on to a new machine, different base url temporarily, convert it to DC and then when it's looking healthy, swap it with the production machine (rollback is easier if you…