Nic Brough -Adaptavist- Expert

Have you copied leading or trailing spaces (or other stuff) in the ID?

The REST API does have some workflow editing capabilities, but does not yet have complete access. See https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-group-Workflows

But if you order by something other than rank, it's a logical impossibility to change the order of the list by something you are not looking at and may well make no sense.

https://library.adaptavist.com has loads of example scripts that read and write custom fields. Start by borrowing some of those.

What do you mean by "add"? Attaching xml files to JSD is working fine for me and that's all I can imagine you mean by "add". So if you mean something else, you'll need to explain what it is. And, whatever "add" means, "can't add" tells us nothing about the problem. This morning, I "could not add a file to Jira" because my…

You'll need to write a listener that picks up "issue moved" events, looks at the issue change that triggered it and apply the new label if appropriate

There is no "better" way - you're choosing convenience at the cost of inefficiency

That code will work in a couple of older versions of Jira, but only in a couple of places. In more recent versions of Jira, you're going to need to write a lot more js code, and bear in mind you will need to write different code for every place where the field might be editable. And think about how you might control REST…

The change log records changes to the issue. Viewing an issue or cancelling an edit do not lead to changes, so they're not recorded.

Ok, so why are you looking at roll-backs? Why do you think you need to do that when you're creating tasks?

Issue type is not just a field, it's one of the two things that all the configuration hangs off. Changing the issue type can be a massive task. You're not just changing a bit of text on a post-it note, you could be trying to change a bicycle into a zebra. The warning you see here is happening because the issue types are…

I'm afraid you are absolutely wrong. That sounds blunt, rude and aggressive, but I am trying to keep the answer short. Jira admins can not create any hierarchy (beyond the minor points of being able to effectively enable or disable Epics, Categories and Sub-tasks) I would be very interested in where you got the…

Or you could work with what you signed up for? Seriously, you are defending bad client behaviour. Stop.

Plain Jira Core does not have a way to do this, but when you add Portfolio to it, then yes, you get all the initiative/theme/your-layer functions on top. (And Align - that handles it even better)

What "other means"? If the contact details are no longer valid, what are you expecting them to do? If you read the T&Cs, you'll see that it's your responsibility to provide valid contact details for accounts. Yes, it's well buried, but it's also a common-sense assumption when you're getting services from an organisation.

That error message is not unusual, and could be a number of things This one is saying your build computer (your machine I'd guess) is not able to go out over your network to the internet and fetch some files. This is either a problem with your networking, or that the files it's trying to fetch are not where it is expecting…

Ok, it's good that you've got the domain verification sorted, but I completely understand the bad side - the worry that you might lose something. I would log into the main account for most.us.co and have a look through the list of things it has access to. For anything it has (and you want to keep), make sure that the other…

ScriptRunner, plus the library script I pointed to earlier is the solution I've used a few times, and I suspect other people have as well.

Obviously, I'm going to say ScriptRunner, as I work for Adaptavist. Obligatory marketing out of the way, I'd say that most apps for Confluence are really good at modifying it in specific ways. I don't think there's any app I can say "everyone should have this". ScriptRunner is great, but mostly for automation and back-end…

The facts are that the error message you are seeing is generated in the two cases I described.

No, it's a help-desk, not a contract management tool. People have done this though, usually with a scripting or automation app that can count up the hours spent or number of calls by client and check on that when new issues are being created.

Quick filters do not work that way. You set them up with a selection or query and then you toggle them on and off to narrow down what's on the board. You don't get to select variables for them.

It's because the "filter =" function runs the query many times, stores the results and then has to re-read them again when it matches the other clauses.

They only do that after warning you several times when you have not paid the bill.

Ah, I wasn't sure. There's a "server" link at the top right which drops down a list of all the versions of JSD Server so you can get the right one (although the functions haven't changed a lot)

Nothing. As you can't change the hierarchy, there can be no impact.

Yes, that's what my original answer said.

Customer accounts are unlimited and do not cost anything. See https://support.atlassian.com/jira-service-desk-cloud/docs/receive-requests-from-an-email-address/

The forum posts you have found have given you the answer. There is no alternative - a staging Cloud environment can only be another Cloud system, and the only way to populate it is to export and import.

You can add Epics to Jira Core, but they won't behave as Epics from Jira Software do, it's just another issue type.