Nic Brough -Adaptavist- Expert

That is the Server version. Jira has three flavours - Cloud, Server and Data Centre. (A poor choice of names from Atlassian as they mean different things in the rest of the world of computing). The version of Jira Server you have is 7.1.2 I don't know where you're looking to get that 3.4 to 4.6 list. Your best option for…

Yes, you can use include to represent "external" pages on "internal" ones. Be aware that you can not go in the other direction - if someone cannot see a page, then "include" respects that - if they run into a page that includes another page that they cannot see, then they get a little placeholder saying "you have no…

Ok. There's a couple of essays as responses now. They're good topics, but they show that the authors do not understand Scrum estimation and commitment. Please, go read the Agile manifesto, dip into a bit of SAFe, Lean, Less, DaD, etc if you have to, but please please, please go read up on what to estimate and how to talk…

The issue history is available for each issue in the history tab. There is not a lot of reporting on it, and even less if you've deleted the field.

Edit the workflow you want to make it mandatory on, going into each transition that moves an issue from one status to another, and adding the validators into them. You will need an app to give you a validator to check that it is filled.

That will not really help you track, as it's not recording a user or their activity, just some arbitrary tag. You can log in many times, you just lose all your tracking.

I do not know what you mean by "snap". If you want to re-assign an issue to someone, change the assignee. If you want to change your associated user (artist 2), edit that field instead.

Yes, because you are moving them from one project to another. If you want to split them and move the new half, most people will clone and move the new one. This does, of course, make them entirely independent of each other.

No, that would be incorrect, as the value of a cascading select is the pair, not half of the value.

An "unsupported" plugin could be doing anything. Atlassian verified ones have been through some security tests, and are known to be backed by trusted organisations, but unsupported leaves the door completely open.

Security levels apply to issues, not to requests (which are what customers see in the portal). If you don't want them seeing each other's requests, lock them down to only see their own requests or that of their organisation.

I do agree that the multi-select is not great when there are a lot of options. But if you're wanting to limit people's "tags", you probably don't want a lot anyway. Ideally, yes, we get a type-ahead for multi-select instead (or better, as well as, and we can choose which we use). But the fact remains if you want to control…

Technically, you can add loads, but you will find pages begin to slow down if you go too high. That will probably be way higher than your people can find useful in a single select (a cascading select is harder to max out for people, as the first layer helps break up the results a load, but still, if you're hitting more…

And if they're setting it during the transition, you can use almost the same code/config for a "validator"

JSD adds a swathe of functions and a couple of custom fields, and locks. If you remove it, it will leave the additional custom fields behind, but should remove the locks on existing fields. (Although I don't actually think there are any, I think it only locks JSD related fields)

No, you have to be an admin to be able to create projects. There are a couple of apps in the marketplace that allow some forms of delegation.

Under <jira home>/logs - it's atlassian-jira.log. You can get <jira home> from the system information page.

You can always report across projects, yes.

I tend to include "reporter" in the security scheme, so that no matter what the level is set to, the person who reported it can see it.

Admin -> Issues -> Custom fields -> find "business function" and click on the "configure" link for it. You'll be able to edit the departments, add them and disable them if you no longer need them.

If you want to use the new user macro solution, it's admin -> create user macro -> give it a name and type, and literally have it do nothing in the result. That helps if you've used the macro in pages rather than in the layout like the other two questioners had.

I get the same on Cloud

It is very hard to answer that question by digging through the database. In the UI, go to global permissions and look at whom has "use confluence" and "administrator" access. The combination of those users and groups, minus deactivated people will give you the number of users chewing up your licences.

You don't. Jira and Confluence are very different systems with very different access models. A lot of the permissions in one of them have no analogy in the other. What you can do is use a shared user directory and set up single groups that grant various access in both systems at the same time, but that's about it.

Those are not projects, they are issues, and it's impossible to work out what view you are in from the limited screenshot, so I can't tell if it's something in the reporting you are doing or you have an app that is doing it.

I'm afraid there's no way to do that. A clone really does the absolutely minimal flat "copy the old issue"

With a lot of work, you can do this. In some cases and with a lot of effort. Have a look at the issue history - this records almost all changes, including a plain text "option X was removed because". You'd need to extract that, convert it back to options and then re-apply it where you destroyed it.

The pop up is quite strict, but probably accurate. Atlassian are not going to put a kill-switch into the software. But they may well use code in the installers or installed system that will not run on the unsupported platform, and they're not going to test to see if they've broken anything for that platform. They won't…

No. I do when I pick up a new Jira where no-one has thought about it, but log in as an admin, go to Admin -> Issues -> Priorities and changing the colours and icons to something better differentiated fixes it. It is well buried, but you can customise them to death. I'm particularly fond of changing the icons to pictures of…

The board would need to be rewritten to constantly monitor the entire message queue and react to any changes. This is not a model Cloud can support at the moment, it requires a lot of code change.