Nic Brough -Adaptavist- Expert

There aren't any supporting libraries, you are going to have to write a massive chunk of Confluence functionality into your application.

You don't. As I said in June, Next-gen projects do not have workflow like Classic. You can't convert project types either. Closest you can get is to create a new project of the other type and use "bulk edit" to move all the issues from the old one to the new one.

It can, but see https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html for how to do it - you won't be using the GUI to do it.

Indeed, if you are using Server or DC, the version is very useful. If you are on Cloud, untick the box and forget it - it's irrelevant. To get the version on server, the easiest route is Help (blue question mark, top right) -> About. The version in there is what the question is about, as you had surmised already.

watcher = currentuser() as an "advanced search"

This is the same answer as we got to when you asked over in https://community.atlassian.com/t5/Confluence-questions/Confluence-server-showing-IP-address-instead-of-subdomain-name/qaq-p/1466308 and some other places. You need to put the directives from the error message into the proxying connector, and you need to follow…

I have - and they fail because you have people looking at different views. No-one I've seen using these (well) has different backlog views for different people.

You would need to effectively recreate most of Confluence's code in your application, with all of its supporting libraries and tech, and get your application to handle a REST connection to Confluence such that it can get the working data out, and push changes back in. I'd strongly recommend just using Confluence, I can't…

If you have a different workflow for Bug and Service Request, you can do this with workflow properties. Assuming they currently have the same workflow, then I would copy the current workflow and rename the copy to something like "limited service request". You can then add Workflow properties to each step, limiting the…

You can't assign teams to issues, so it wouldn't do much for you. The point of a queue is that it is already being looked at by a team. In most places, Agents would self-assign when they pick up the next issue in the queue, but many have a leader who will sometimes assign for the team.

Not quite. I do not think I was too clear. To keep it really simple, I would create two new screens, one that includes Reopen count, and a second that does not (Actually, I'd copy the screen you currently use for task twice, and modify them). Call them something obvious like "task-with-reopen" and "task-standard" (New…

The gadget does not seem to think that is the case - it's seeing 23 issues with two values for stream. Best way to investigate this is to do what @Manon Soubies-Camy suggested - click on the links to check the JQL each one is running off. I would look at the "server" line first - it's only got a few issues and a…

Are these the built in boards, or are they boards provided by a test management app for Jira Cloud?

People will always see all the columns on any board they can see. You might be able to make columns look empty with "issue security", as Jira won't show cards in columns if a user does not have the permission to see the issue behind the card, but that does mean you'll be hiding the issue from the user in all places. But…

Missing token happens most often when a session has timed-out. If, for example, I go to an upload process and give it a file, but don't finish the process, then hibernate my laptop and wander off to make tea and do some shopping, when I come back and resume, then I'll get that error when I click "upload".

Set the quick filter to JQL and enter either "Status = open" or, if you want do do it from the end states, "Status not in (closed, done)"

Not the recipients by request type. See https://confluence.atlassian.com/servicedeskserver/managing-service-desk-notifications-939926348.html for what you can do

I would take a look at "Questions for Confluence", it's not quite a forum, but it does a lot of stuff similarly to the way we tend to use this place for questions (and was actually the software behind the previous incarnation of what is now Community). The other thing to look at is…

That's the answer then. Imagine a simple case where you have a single issue with "server" and "licencing" selected, and you have only that in the gadget. This is a single unique issue, so you'll see two lines, one for server, one for licencing, both with a 1 in a status column. Total unique issues in that status = 1, but…

You have a field description of "." on the Severity custom field. You can change that in the custom field settings or field configuration for the issue type.

Your server.xml files are not set to use the proxying connector. 

My guess is that you have not got the changes to the server.xml correct. Did you make the suggested changes in the proxying connector?

Talk to a certification authority, or use self signed. Google will find you a good list of the reputable authorities, and if you want it cheap, "letsencrypt" has rather a good product, growing in popularity. For installing them…

Indirectly, yes. Workflows can be tied to projects, and workflows can control the list of resolutions used. You still need the full global list, but workflow properties can be used to either include specific items from the list, or exclude some from the list. See…

You'll still need to ask Atlassian if they are going to provide a way to enable it in Cloud.

"false" is a very flat property, you can be a little more clever. From memory, jira.permission.comment.group = my-group-of-agents is probably what you are looking for. Even if I'm wrong on the detail (or spelling), I think that shows you the principles of permission properties. Proper info is over at…

Queues are connected to service desks, not teams. Teams should be aware of which queue(s) they need to be working from, but that should be simple, as it's the ones in the service desk they're working on or the ones their team owns. What were you intending to get from linking teams to queues?

My best guess is that an inexperienced admin has added a resolution called "unresolved" to your list of possible resolutions. Any value in the resolution field means the issue is resolved (and hence struck out). Open, Closed, Purpli, "£^£, unresolved, not done, etc - absolutely any value says "this issue is resolved". This…

No, there's no way to limit it, that would defeat the purpose of global ranking. You can restrict the usage with project permissions, but as you say, they're not necessarily going to work if a board is drawing issues from more than one project.

I think you might have to fix this by changing the output of the scripted field. I think you have selected a type of field which has formatting that relies on Jira's UI code to be rendered usefully for the users hitting the web interface, but Confluence does not know that this data needs to be rendered, it displays the…