Nic Brough -Adaptavist- Expert

Swimlanes and quick filters both use JQL and it's probably the same query for both functions. If, for example, you set up a quick filter for "issuetype in subtaskIssueTypes()", then when a user clicks it, the board should hide all the issues that are not sub-tasks. The same query, when used as the first and only swimlane,…

If you're having to restart the service to get it to work again, it's not a database problem. The database query activity is a symptom, like slowness for the users, it is not the cause of the problem. You will need to start looking at what the service is doing overall why it is being slow. What are the users triggering…

See https://www.atlassian.com/trust and https://www.atlassian.com/trust/compliance

I think https://scriptrunner-docs.connect.adaptavist.com/confluencecloud/quickstart.html gives good examples of what it can do - I have to admit I've only ever used SR for Confluence Cloud for page event scripting (create issue/project on page create) and some housekeeping type things.

Sorry I can't give you a direct answer to the last bit, I don't know Automation as well as Scripting.

Edit the issue and select a security level. It may not be in quite the same place 5 years after the last discussion.

Log into your Cloud system as an admin and then go to Projects -> Create project. Hit "change template", select "Service project", then look to the bottom of the list where you can swap between "try a next-gen template" and "explore classic templates" I suspect what you really mean is that you have not created any JSM…

There's two parts to that. The easier one is "not done" - a simple search can do that with (pseudocode) "parent = X and status not 'done'". The hard part is "next" - whilst we could add "order by" to the query to get an ordered list, you haven't defined what that is. Assuming the order is something easy or obvious like…

How are you telling Jira what the "next" sub-task is?

Nope. It's a Service (whether it's DC, Cloud or Server) running and listening for people or systems to talk to it, either over the UI, REST or even email. It doesn't care what route you talk to it over or what version you're licenced for! If you want to use routes other than the three main off-the-shelf ones, you might…

There's a bit of an essay on what database pooling is, but the short version of it is that a connection can only handle a certain number of channels talking to the database at a time, and Confluence is trying to go over that and it is failing. You are using the internal embedded database, h2, which is not supported and…

Check the authentication docs at https://developer.atlassian.com/server/confluence/confluence-server-rest-api/

You can do that, but the other custom field won't have the same attributes as the assignee field, so it really remains a second class thing. It is something I meant by "indicating secondary people who are involved"

Core projects have a simple and non-configurable board attached to them. But when you use a Software project, you won't get to it, you'll be taken to the Software boards.

No, it's built-in and always available.

Nothing you'd really notice. I tend to think of JSD and Software as adding layers of functions over the top of Core projects, rather than being different things. There are a couple of things, but they're functional rather than data related. For example, Software boards block the simple boards Core projects can have, but…

Although if you archive a value, you will no longer be able to add it to issues (issues having it will retain it)

Ok, so there was a big clue in my question then. Stop trying to fetch data from a field that is not a custom field using a function that can only fetch data from custom fields.

I'm afraid saying "I want" with an explanation of your sub-task ideas adds nothing. It would not be in the slightest bit helpful if it breaks your process. It does not work that way, you need to have a read through the earlier comments to see why it's like that.

"Working directory" is usually the directory the application server is running in (The Tomcat, not Jira). There should be a full path labelled "Jira home" in the system info page

Sort of, but it's two separate services. * You've got a server licence * You buy a subscription to a Cloud instance If the Cloud is replacing the server though, you can have a talk with Atlassian - they can credit your remaining server months payments to your Cloud account if you shut down the server.

Nope, not a user there.

You do not, as Ismael already said.

You can install upgrades, but only ones released before the end of your licence term.

To be able to see the charts, the users must be able to see the issues the charts are being generated from. If they can see those, then they can work out what the charts show them for themselves. So hiding the charts from your customers is pointless. In fact, it's a retrograde step, as if they're interested, they'll focus…

Last time I ran into a request for replicating Service Desk without using Service Desk, it worked out vastly more expensive. JSD for 10 Agents was a lot cheaper than the 1,000 user subscriptions to the swathe of apps they needed.

I'm sorry, but that's not quite right. To correct Mike's post: * The SD licenses basically let the SD agents see the queues and the normal Jira-ish detail view of the tickets in there. They also allow the Agents to work within the SD projects (Core users only get view, comment and participate) * They get Jira Core by…

No, it does not, because it's not a service desk app, it's just for SLAs. There are no apps I know of providing a portal type thing. Could you explain why you are discarding Jira Service Desk as an option?

Go to id.atlassian.com start.atlassian.com or one of the other sites you've got access to via the account, and look to the profile icon. In there, there is a "manage settings", go there and select "account preferences" and you'll have the opportunity to delete the account.

Server licences and Cloud subscriptions are totally different things, not really worth even talking about together. I am not sure what you are asking about on the server side? When you get a Cloud trial, you can use it for a while and, yes, when you're ready to buy, you get the subscription and your trial site simply…