Nic Brough -Adaptavist- Expert

Ok, so what error are you getting when you click "delete"?

There's no way to do this (and you'll almost certainly just break your Jira if you try to do it in the database) It sounds like you are building over-complex security schemes. Why do you need loads of new levels? Why so often? Why are you not sharing the scheme across projects?

Oh, yes, it does that now. You'll need to add one option to get started.

No. The concept of "done" is for the board that the sprint belongs to.

It does, if the field is of the right type! You can say things like: * Assignable user = user called Alice * Assignable user = Group called "Bob's friends" * Assignable user = Role called Developers * Assignable user = Group-picker field called "Based on Group" The trick is the last one - if you select group "Alice's…

True, but they've also told us Server and Cloud at the same time, and not even described how they know it is "not starting". Are they looking at the command that starts it? Or does "not starting" really mean "I can't reach it in a browser"? Or that an angry penguin is sitting on their keyboard so they can't get to it?…

Please don't say "resolution status", it's nonsense in Jira-speak because resolution and status are two totally independent things. Or you might even mean the name of the "Done" column?

How have you implemented the "name of transitioner" field?

Assignee options are controlled by permissions - the permission scheme has a line for "can be assigned issues". You can use fields and groups in there (assuming it's a company-managed project)

I know that, that's why I was explaining that there's no such thing as "move" between sites. The separate subscriptions ARE separate sites.

You can not do this on the most part. If you change the workflow that a board is looking at, you will need to update the boards to take account of your changes. They have no way of knowing which column you might want new status to go into, or that any removal of status means you want an empty column (you might be wanting…

To be clear on a technical bit of this - there is no "move" between separate sites, even when they're owned by the same organisation. A "move" would actually be a "copy, then delete". Synchronisation, rather than "move" is the best option here, as @Dave Mathijs says.

Some places find it useful - after all, the assignee is the one person currently responsible for dealing with the issue, and it makes sense to say "you reported it, it got fixed, so it's yours again now". But it's just as valid not to bother - the assignee field will then contain "the person who was last responsible for…

>When the issue type compliment is selected the PH# field shows as required Jira does not do that natively (dependent fields), I suspect you have got Scriptrunner installed and you have set up a "Behaviour" to do it. Behaviours can make a field mandatory in the UI, but do not touch the field configuration. Ask your admins…

There's nothing we can do with "Jira Core on Cloud is not starting". You have not given us any information to work with.

That's up to you and your organisation! We, the Community, can't tell you where your stakeholders might be listed, or anything about who they are. They could be customers or licenced Jira users, yes, but you'll have to define where you get the list from.

Welcome to the Atlassian Community! The documentation is accurate. There is no "delete category" because you don't need one. Remove the unwanted category from each space that currently has it. The category will disappear.

Yes, you need to have a permission to be able to create one. As an admin, go to Admin -> Global Permissions and click the "users" tab - it'll list all the groups and tell you whether they have personal and/or general space create permissions

Yes, apps for DC need to consider a few more things than Server apps. There's a good list of areas you need to look at when writing for DC over at https://developer.atlassian.com/platform/marketplace/guidelines-for-data-center-app-development/ However, Server apps have a remarkably similar list of things to look at. It's…

Welcome to the Atlassian Community! Confluence is a wiki, a documentation system, it's not for handling lists of things like CSV, spreadsheet, issue trackers etc are. It's expecting imports of text (often with some level of formatting). You could "import" a CSV file as text, but all that will do is give you a page with a…

Ok, good, but that's a cloned issue - the clone process will have filled in a summary already. Have you removed it from the display in that screenshot to hide the content? (It's fine to do that, but it looks like it's blank, rather than obscured). Assuming that is the case, then would it be fair to say the need is When a…

Welcome to the Atlassian Community! Despite the use of Trello, this is not an Atlassian question. Even if it were, we're a community of Atlassian users/fans, not support (and certainly not lawyers or police), so we wouldn't be able to help you anyway. You'll need to "complain" somewhere else.

The sub-tasks with their parents is because sub-tasks do not have a global rank themselves, they are part of their parent issue.

What do you mean by "escalated to another project"? Please tell me you're using "create linked issue" and not moving the issue as part of a standard process?

You've asked this as a question elsewhere, that's a better place to get an answer.

Not an answer, but could you clarify what you mean by "rule" - is it an Automation rule? If it is, can you tell us where you are getting it - on any action on all rules or only certain rules? Project or global rules, or both?

Welcome to the Atlassian Community! What do you mean by "week wise"? My guess is that is about the display of the issues. JQL does not have anything to say about how you display the results of a search. You will need to use your search in a display function that supports grouping by week. The issue navigator (the grid-like…

Welcome to the Atlassian Community! This sounds like you've got quite a complex process with people demanding fields be filled at certain points in the flow. That's not a problem in itself, but it is a problem for your current exercise. To me, it sounds like you are trying to do some "housekeeping" - you've got a big pile…

I'm afraid there is no simple way to do this, it's an unusual thing to do, and hence no-one has written any code to do it. (It's unusual because it sounds like the data structure is the wrong way around, and you probably shouldn't be using 34 fields, but obviously, I can't say that is the case without knowing what you're…

Welcome to the Atlassian Community! Does this happen for other apps, or is it just the groovyrunner? If it is only groovyrunner, then is there more errors following the failure in the log?