Nic Brough -Adaptavist- Expert

Because the permissions are done at a global level. Allowing a project administrator to be able to change permissions on everyone's projects is an unworkable disaster and would defeat the whole point of having administrators. It is restricted to administrators because it's a global configuration. If your admins use roles…

Jira does not have field level security. You need an app in order to do this sort of thing.

If the comment area is not showing when editing or transitioning, then you don't have permission to create comments. Check the project permissions.

Boards are not containers for issues, they are a view of a selection of issues. If you don't want an issue to appear on a board, you need to put data on it that can be searched for, and then adjust the board filter such that it does not select issues with that data. If the data you want to drop things off boards is the…

If you look at the admin pages for each area, you'll see most divide the list into two - active and inactive. It is a little boring to run through clicking on each, but you can safely delete every "inactive" item.

Jira includes global fields in all projects by default. I don't quite understand the problem you describe though: The Field configuration is one way to tell it to hide a field if you don't want it in a project. "Restrict to", as a custom field, can be hidden away from projects with the context or the field configuration.…

Again, do not do that. A post-function is the wrong place to try to do this. Do it in a validator. It won't work because post-functions are not the place to do validation and they do not support it.

It's the same answer - you don't, because team-managed projects don't use custom fields from apps.

I've done the first option several times - a secondary DR Confluence set up in a second data centre somewhere away from the primary. Most of the time, it's been a full DR solution - we're replicating Confluence because it's a production system. A few times though, it's been "DR for the Confluence docs that are about…

Cloud has automation built in, so you could look to using that for some of of what you want to pre-populate when you create new issues. The REST API is always available to you as well, no need to ask the admins if it's there.

You've run into one of the things documented at https://scriptrunner.adaptavist.com/latest/jira/releases/UpgradingToJira8.html - that doc has lots of fixes for other things you may hit as well as this one.

What does the application log say the problem is? (<jira home>/log/atlassian-jira.log is the first place to look when it fails to start)

So the first thing to do would be to stop reading the docs for Cloud Jira when you're using Server/DC. I know it's a bit confusing having two separate products with the same name, it is very easy to land on a doc for the wrong one because of the name and that the docs are in the same place, but we should all be checking…

You will have to redevelop them, you can't upload Server apps to Cloud, and the framework for loading Cloud apps is completely different to Server. I would take a step back and look at each app you've got, analysing what it does and how people are using it. You probably then want to look at whether Cloud can already do…

An issue collector will try to use the reporter's Jira account for reporting the issue. Using an issue collector would bypass the need to pre-populate anything, as you could set it to use an issue type where you've already defaulted all the data you want to pre-populate on issues coming in that way. Going back to the…

For the "why" - team-managed projects do not use the global custom fields. Their local fields are implemented totally differently and are not the same thing as the global custom fields.

The original question and answer were for Server Confluence, you are on Cloud, where you can not turn it off.

What do you mean by "list view"? What do you think is missing?

Only admins can add billed products to your Cloud site or servers.

This means what it says - your licence is coming to an end and you will not be get support from Atlassian, not upgrade your server to versions released after the end date. Your server will continue to work, you're just unsupported. If you want to be supported, you will have to renew the licence.

Go to the project settings and find the field configuration scheme. You can flag the field as "mandatory" in there.

Jira Server is going away. It doesn't matter where you are running it (your own machines, AWS, Azure etc). Jira Data Center will continue to be supported on all the platforms it currently runs on.

You need to look at what each app does, and then work out a way to translate what bits of it you are using up into Cloud. This is not something you can have a simple one-page answer for.

It does, a bit, I think the next thing to look at are probably "issue collectors" - that's code you can add to non-atlassian sites to pop up questions for your users when they get stuck (but I don't want to rule out more things, or stop the conversation here - if these don't work, there is a lot more to look at)

I have seen similar things a few times over the last few weeks (most of the Adaptavist clients I am usually engaged with use Zoom or Slack, but I'm currently embedded with clients who do a lot of MS-Teams) There seems to be something about Teams that chews up our bandwidth for no reason I can see. While this is not an…

No, Jira Software's hierarchy is Epic -> Issue (story) -> Sub-task. You can't insert layers between them, nor go downwards. Adding advanced roadmaps or other apps can layer more above Epic. Structure is the only app I know of that allows you to make it look like there are other layers.

I'd usually reach for Scriptrunner (I would though, as I work for Adaptavist). https://library.adaptavist.com/entity/automate-the-creation-of-complex-page-structures-within-confluence is a server script that does a load of stuff.

Yes, that's saying your Jira is not running, so it can't connect to the user server in it.

I don't know, I don't know what you are trying to achieve here

Ok, so my clarification matches and what you need to be doing is using a filter to select the issues you want to report on. All apps for Atlassian products have to be licenced to match the number of users you have, as all of them could use it. Dashboards have all sorts of gadgets (most of which report off saved filters…