Nic Brough -Adaptavist- Expert

I think you have posted in the wrong place - we don't have the original question you are answering, or any view of what you mean by PRT or what fluid properties have to do with Atlassian.

When you create a scripted listener, with SR, you can tell it what events to react to in the settings. In this case, you'll want "issue moved". Have a look through https://library.adaptavist.com/search?term=listener to see the sort of things people ask to do with listeners, you might want to look at something like "send…

Any that can take a date range as part of their parameters (usually done by the filter more than the report) If you want more than that, I'm afraid your question is too vague as it is. What are you trying to compare? What are you hoping the report will tell you?

I think you have posted in the wrong place - we don't have the original question you are answering, or any view of what you mean by THP or what you're doing forecasting in.

To do what?

It depends on how they are being implemented in Jira. Are you using one of the test management apps to hold them?

There's no way to do this. People can either create issues in a project or they can not. With a scripting app, the best you could do is have a listener that spots moved issues, checks them and reports if someone is doing the wrong thing.

Yep. (Assuming the same profile of usage by people)

You don't get to add services to Cloud systems.

Atlassian use whatever payment method you gave at the time of subscription to gather your payment.

It's not quite by project - a board can include many projects, and if the workflow is simplified by the board, it's a single workflow shared by all the projects. But, yes, you will find that the list of workflows becomes rapidly very long, one for each simplified board. It will not directly impact your performance at scale…

Sorry, but that's incorrect. A user has to be created by the installation, it won't actually serve a login screen up unless you did create the initial user. Anyway, as you've lost this account, please see https://confluence.atlassian.com/jirakb/restore-passwords-to-recover-admin-user-rights-972329273.html That will get you…

How are you getting the issue object? Are you sure that issue has a value for the custom field? Also, your output bears no relation to the script, could we see the actual output?

Yes, but you'll get nothing or everything back from it. Could you explain what you're actually searching for?

You can have a number of accounts active up to the tier for which you are paying for (10, 25, 250 etc)

Probably, but I'd question why you are tracking things in two places, and you'll need to explain what "TC" is. Top Cat?

You create an administrator as the first user when you run the installation. If you're adding Service Desk to an existing Jira Core, then your administrators already exist (and it's one of them who are adding it)

No, there's no layering or grouping in organisations (yet)

No. Best you can do is alter some of the colours in look-and-feel, but that won't get you a dark page.

This looks like you simply want to change the assignee? Or am I misunderstanding the question? (If it is just the assignee, then make sure you have the permission "can assign" in the project permission and then just click on the assignee field)

That's fine, but it is the wrong thing to do as a column. Columns should represent where something is in a process, not conditional stuff like who should be looking at it. You should use fields on the issue to indicate the team, and then use swimlanes based on that field to separate them out.

Same answer - the permissions are not that granular.

Try giving the plugins longer to load In setenv.sh (or .bat) in <jira install>/bin, look for the collections of parameters that have -D at the front. Add -Datlassian.plugins.enable.wait=300 to the list, which gives the plugins longer to load. You may also want to try increasing the amount of memory available to Jira.

You don't really. To-do means it needs some attention. It has nothing to say about who should be looking at it. Generally, you should think of a board as being a team's work. That would, from what you've said, mean having a board for developers and another for the business team.

You have installed an app which provides a field. The app does not have a valid licence and the trial period has expired, but you are still trying to use it. Go to Admin -> Custom Fields and look for all fields of type "multi level cascading select". Delete the fields. Then go to Admin -> Manage apps, and remove the app.…

Yes. Advanced roadmaps is available for Jira Cloud. If you have premium, it's built-in.

There is no "solution suggested above" I think you are misunderstanding Jira-speak here. A swimlane is a group of issues collected together across a board. If you were to select status as a swimlane definition, you'd end up with a pretty useless board, as each swimlane would map to a single column. I think you mean…

I've seen this in a couple of cases: Most common is when I've left a browser page open on a question for ages and it's timed out (not necessarily my login, for some reason the login timeout seems to be different to a page timeout) I've managed to install a browser plugin that breaks it for no good reason I can find

The permissions are not that granular. You can't remove bits of them like this.

There is no way to do it - an administrator has admin rights and is hence offered all the administration options.