Nic Brough -Adaptavist- Expert

Like all the other options Reyvz can only pick up deleted data from the time you install it. But if you really want to let your people delete issues without checks, it is a very good option for avoiding the data loss - it makes the backup and restore a doddle, and, of course, tells you who deleted what. 

Ok, that narrows it down a lot. As the message says, it is either not on the screen, or unknown, and there are two ways to do that. The "not on screen" message tells us that you have a custom field that is set to be mandatory, with that ID that is not on the create issue screen. One of your admins has removed it from the…

Welcome to the Atlassian Community! Projects can be configured to offer different sets of issue types. Have a look to the bottom left, you should see "you're in a Company-managed project" or "team-managed project" For both, go to project settings, and look for "issue types". TMPs will list all the currently available ones…

The Community here is not support. On my part, I only do support calls as part of a Consultancy engagement, or for Adaptavist products customer success. If you could give us the full text of the error message, we might be able to tell what the problem is and walk your Jira admin further down the path towards it.

I'm afraid it does not. It's unhelpful, because it misrepresents the value that the user wants to put in. There are four cases. MandatoryDefaulted What the user should see for "nothing selected" No NoNone, pre-selected No YesNone. But the default will be pre-selected when the screen renders Yes NoNone, pre-selected But…

Hi Jerrod, If you have one of the scripting or automation apps, then yes. There are different ways to do it, depending on when you want to trigger the change, and which app you're using, but if you have a recent version of Scriptrunner with HAPI, then the below will do it Note that: * This script is written for the SR…

Glad to have helped! And rather happy that it worked, because if it wasn't that, I'd have been totally stuck!

Welcome to the Atlassian Community! The sprint field is not as simple as just "current sprint", it needs to contain all the sprints an issue has been through, so that you can report on old and current sprints (but not the sprints that have not been started) You need to use the functions to do this. Try sprint in…

Welcome to the Atlassian Community! No, because the 2FA for an account is always linked to your device, not other people's. That's the whole point of 2FA - it relies on something you know about your account, and something you own and have direct access to it.

If the account is a personal account, and you know you do not need it to access any Atlassian systems (to add to Luiz's list, people don't realise Trello and this Community here are also accessed by your Atlassian account), then you can delete it yourself. Log…

We don't need a video, we needed you to tell us what actions you are taking that trigger the message. You say you get it when creating an issue, so that's great. Can you tell us: * Is it happening for one issue type in the project, or all of them? * Is that the full text of the error? Is there any more? (A screenshot of…

It is the same for DC.

Thought so. You are creating new workflows, not editing the existing ones.

Your parenthesis are still missing. By the way, the way I tend to check is the same as what Dwight did, list out the joined clauses by line, but also, I indent to make it clear where the joins are. The important thing to remember is that a query builds a list of issues. If you only use AND clauses in the top level query,…

Welcome to the Atlassian Community! It's mainly about limiting external software or power-ups from overloading your Trello with requests to see or do stuff.

Welcome to the Atlassian Community! Trello is not an issue tracker, it's a noteboard. You can use it as a simple issue tracker, but you're going in the wrong direction. You would need to add a huge pile of powerups to get it to do even the most basic project management that Jira has built-in! Jira is an issue tracker, and…

Except that you can't convert the select lists to numbers, you would have to write potentially hundreds of "if" statements.

No. The pencil is a "go into edit mode" function. It will not create a new workflow. If you publish a workflow, then your changes overwrite the workflow you edited. I can't find a way to get that display, I think I'd need to see the full text of that line to try to identify where it is coming from. I think you still have…

No, if you did it with a separate project, all the permissions are local to that project. You would have to add all your project admins to it as users, the project would not recognise them by "project admin somewhere else"

It's not even a case of "must be in the same project". A sub-task is a fragment of its parent, not an independent entity. It's complete nonsense to have a sub-task in another project. Imagine having the spark-plugs in your car in a different county to the rest of your car - your car will not work.

Welcome to the Atlassian Community! If you have a more recent version of Scriptrunner, then you can do this much more easily by using HAPI. You have not told us exactly how your select lists are representing numbers in their options, so I've made an assumption, but: <span>def</span><span> issueKey </span><span>=</span>…

Massive changes - Jira Software has changed vastly since it was called Greenhopper. You really need to stop looking at Greenhopper completely. Replace everything you have that might be using its API with REST calls as a matter of urgency.

You can't view what is not there any more. DC logs deletes in the audit log, as Aaron says, but it only logs the key and the person who did it. Delete really does mean delete - there's nothing there any more. Aaron recommends removing delete permissions from Cloud. That is highly recommended for DC as well.

There is an alternative to automating things. Building on @Richard Scholtes answer. * Create the group picker as he said (let's call it the-responsible-team for clarity) * Create a set of groups with the relevant possible assignees in them * In the permission scheme, set the "can be assigned issues" permission to "custom…

Removing the assignee field from the screens still lets people click "assign to"

You would need to change the permission scheme to say "no one but the automation user can assign issues to other people"

What do you mean by "microsoft documents can be used in Jira DC"? What, exactly, are you trying to do? If you're not sure how to answer that, then could you give us a brief description of a user journey? For example "user clicks on something in Jira, they get asked if they want to download a file, they edit it, then go…

Welcome to the Atlassian Community! "no", is the short answer. Detecting "automatic" is the problem. That choice is not actually stored anywhere, by the time you get to a post function, Jira has worked out who the assignee should be and populated the field in the working draft of the issue that will eventually be written…

Welcome to the Atlassian Community! You are going to need to ask your admins what is wrong. My guess is that the Confluence server has been reconfigured for some reason - specifically the user ID system it was using has been disconnected or misconfigured. It could also be that that ID system is offline, unreachable, or has…

Welcome to the Atlassian Community! They were deprecated years ago, which is one reason you can't find much documentation on them. They are gradually being refactored out as the functions they provide change. You should only be using the supported REST API to talk to Cloud systems.