Nic Brough -Adaptavist- Expert

"Order by" looks at how the option list is organised now.

Use options 3 or 4 - project and issue types can have different workflows, and Behaviours can be applied to both levels.

This is a very complex subject, probably better suited to fora that discuss the internals of operating systems. Swap memory is not handled by applications, it is handled by the operating system (OS). Although applications can tell the OS which parts of their memory usage is more suited to swap storage, most do not. You'll…

I'm not sure I can add anything to this @StephanieC - what you've done here is exactly what I would do! Analysis of what you need, build that as an empty shell, compare it to what you have already, and work out how to map the old data structure to the new one when items are moved from old to new structures.

Welcome to the Atlassian Community! None. You should not be reading the database for this data, it's not supportable or going to work in the long term.

Welcome to the Atlassian Community! I think there's a problem with your question. What do you mean by "get" and what do you expect the "get" to give you? An Atlassian "id" is not a simple string or identifier, it's a whole pile of stuff that defines an account.

You will need to * Remove their permission to edit the issue (stops them editing all fields * Remove the description field from the edit screen (stops everyone from editing the field) * Do #2 above and add the "edit description field" as a workflow transition so that some people can edit it * Install Scriptrunner's…

Welcome to the Atlassian Community! How are they trying to "download" reports? What are the reports in Confluence they are trying to download?

Welcome to the Atlassian Community! What do you mean by "the profile was empty"? Can the user not visit their profile and edit their settings?

A backup is not good enough, if you're going to mess with an Atlassian database, you need to do all the other things I've mentioned. You also need to understand fully how the code understands the database, otherwise you are going to corrupt your database. The "optimal script" for creating a hierarchy is to do it in the UI.

I understood your question the first time. As I aleady said, try "order by <what you want to order by>". Order by Satus asc/desc, order by colour asc/desc, etc.

So, the principle of separating "dev" (and "test") from "production" still stands - Scriptrunner has no way to know whether a script is in dev/test or production within the same system, because Jira does not have any concept of it either. You can set up test projects in a production system and lock down or configure your…

Welcome to the Atlassian Community! You do not have access to the database on a Jira Cloud instance. I suspect what you mean is that your organisation is running Jira Server or DC on Cloud "hardware" (AWS, Google compute, Azure, etc) and you have access to the database node(s) On that, there's a very simple rule - you can…

Welcome to the Atlassian Community! I find the most intuitive one for most of my clients is a mix of all three of those. Sometimes the target status name is good for describing the transition into it, but quite often the best name is a verb-like name, something that describes an action that your users intuitively grasp…

Confluence does not have a concept of "folders" for attachments. Files are simply attached to a page, and listed as a single list, albeit it does version them. The best thing you can usually do with docs is import them as pages, which, as you say, could be structured in the same way as your file lists (after all,…

You'll either need to get an app that enables scripting within your Jira, or read through https://developer.atlassian.com if you want to start writing an app for this. Or use one of the marketplace apps that can help you.

Welcome to the Atlassian Community! There's no way to do this, editing the history of what you recorded is not something an issue tracker should do.

Your "QA approved" status is misconfigured. First, by definition, an issue cannot be "done" if it has open sub-tasks. You should configure your workflow such that it won't let people move an issue into "done" unless all of its sub-tasks are done as well (or train people not to do it) Second, I suspect your "QA approved"…

Ok, so you need to add the "Summary" field back on the create screen for Tasks. Or, if it is a custom field, make it optional in the field configuration.

I'm afraid the response here is completely wrong. Sub-tasks inherit their security level from their parent. This is because sub-tasks are a part of their parent, not separate issues, and there's no value in being able to hide parts of an issue.

Welcome to the Atlassian Community! You need to talk to your server admins - they appear to have installed Jira inside a web server content directory.

Welcome to the Atlassian Community! No, you'll need to code your application to support the length of tokens. (128 is pretty much a standard minimum length nowadays, and you should expect to see longer ones in the future)

Welcome to the Atlassian Community! Backlogs do not contain people, they contain issues. So there is no way to "add a person to a backlog" If you mean you want someone to be assignable on issues in a backlog, then you need to add them as an assignable user in the project(s) the backlog is looking at.

We need to know where you are seeing this error - a partial screenshot of just the field does not tell us that.

Welcome to the Atlassian Community! Are the issue types that are missing sub-task types?

Automations should be indexing issues automatically, so we'll probably need to see exactly what automations you have created, including triggers, and exactly what they try to update.

Welcome to the Atlassian Community! Have you given it a few minutes to get going and then tried again? If you have, then the best thing to do next is raise a support request with Atlassian from https://support.atlassian.com/contact 

You said "summary", not "Summary" in your error message, which suggests that you've got a second field called summary, which is not on the screen. Or it's a typo, you didn't copy and paste the error directly. I think we need a screenshot of the error if the problem is not a "summary" field, and we need to know exactly what…

Welcome to the Atlassian Community! You will need to add the summary field back on to the issue type's "create" screen or field layout.

If a refresh is not updating the view of the content of a field, then the most likely explanation is that your code is not actually changing the field, or if it is, it is not causing the issue to be re-indexed.