Nic Brough -Adaptavist- Expert

The built-in post function is called simply "update field" and it's the same one for setting and clearing the resolution. When it's saved though, it will show as "set the resolution to <xxx>" or "Clear the resolution" in the list of post-functions. There's an example of the clear in the Jira system workflow (the one you…

If the Confluence is from 2014, then the XML is likely to be in a shape that is too old for Cloud to read, it can only cope with exports from Confluence 6 or 7, and it's not good with 6.x exports (actually, it can handle older ones sometimes, but it depends on certain content not being used) You'll need to restore your…

As Ravi says, "customfield is empty" will find issues where the custom field is not filled. You'll need to repeat it for each field you want to check. 

No, we can't help you, we are not your administrators. You need to talk to the administrators of the system, the site "owner". Only site administrators can add more administrators (Atlassian Cloud systems cannot have no administrators, you don't add one after creating them, the person who commissioned the system is…

Edit - sorry, ignore me, answering the wrong question

Your admins will need to grant access to the account, it's currently not allowed to use your site.

Bear in mind that if you do this, it will crash when the numbers hit an issue that already exists I would move the high-numbered issues out to another project before changing the number on the project. (see the project table in the database) I would also want to find out where the emoty numbers are coming from, or there's…

Are you talking about the "message fields" from the Jira Toolkit? If so, how are you configuring the field you are setting up?

Sorry for the delay, this one slipped past me. You'll want to read the change history for the issue, if that has any "component changed" lines in it, they will record the from and to, so you can read the earliest one of them for the "from". If there are no lines in the history for component change, then you know that the…

Don't try to botch it, you should use the existing working functionality for this. Add a cascading select field and look at converting the existing data into it.

"unable to proceed" tells us nothing about where you are stuck. All we can do with no information is suggest that you work through https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html

I would use a REST call to update the page - see https://docs.atlassian.com/ConfluenceServer/rest/7.11.0/#api/content-update to see how to do that

You could use forge to create a field that supports edit restrictions, yes.

There's probably something wrong in the implementation of Edge on your tablet, or possibly something on the tablet interfering with it. Something that has worked on some tablets is turning off "Windows Ink" -- it interferes with drag and drop code in silly ways (I wish Microsoft would try the industry meme called…

@Robert Horan As an Adaptavist, I agree with you, the best way to fix the problem is to get Scriptrunner, but it does cost. As someone remembering their non-Adaptavist days, I agree with you, this is something that should be built-in. When a sub-task takes its values from its parents, it should show them.

Have you added the story points field to the create, edit and view screens for the issue types in the project?

It could also be the fields, similarly to the workflows - to allow "edit" of the issue type, the source and target must be using exacttly the same field confiugartions and contexts.

I am sorry to have to say that business boards simply aren't that configurable

No, the templates are used globally, not per project. But you could add #if $issue.getProject() == "xyz" ... #else ... #end to them, or even use more clever logic

We can't give you a clear answer to this. It depends on the app you are adding. Some apps are small, you won't even notice that they've been added (in terms of memory or performance). Some apps will trip your Jira from "takes a while to start" to "fails before starting because it is out of memory" It is a complex process,…

This is (usually) what it says it is. You are telling it to set the custom field with id 10011 but it is not on the create issue screen. It might not be on the screen for several reasons though - genuinly not on the screen, but also if it's got the wrong issue type, the screen will be wrong, or if it's not the right…

With this particular database hack there are two main risks 1. It probably won't work. It certainly won't work without restarting, and if you're doing that, you might as well do it the supported way, as it's quicker, safer and more reliable. 2. It encourages people to do things in the database. Which is a very very bad…

There is no Behaviour equivalent for Cloud. I am sorry to say that you simply can't do this sort of manipulation of field on Cloud. There are some apps in the marketplace that provide fields that get you some of the way to doing it though.

There is no read only property for a field. To do "create, but then never edit", just remove the field from the "edit" screen. People will no longer be able to edit it with the in-line edit and as it will not appear on the edit screen, it can't be changed there either. For Next-gen projects, you can't do this though, there…

If you remove all the sub-task types from the project, it will go away, otherwise, no. Is there a reason you want to remove it?

Are you asking for someone to give you a list of every possible risk of using a Cloud system? That's an essay question, and one that should be answered within the context of why it is being asked - a risk for you might not be one for me. 

Depends on what you mean by "easier"? Any page can be moved between spaces by hitting options -> move -> select target space and page. (And dragged around in the tree in space content tools if you can't remember which page you want it to land under) Are you thinking of another way to do it?

Yes, you can do that with Admin -> Issues -> Issue types to create them, then go to the issue type scheme to add the new ones to the project. You'll need different names for them, but there's no problem having many issue types

Volume of issues is something to think about with performance, but it's not a lot worse than volume of random inconsistent and functionally useless custom fields. As an admin, I'd rather deal with "a huge pile of probably useless issues" over "a huge pile of definitely useless custom fields". Custom fields have a much…

There's so many options and possibilities here, there's no way to have a single document. You'll need to narrow down the technologies in use before anyone can point you at the areas of documentation. To get started there, there are two things to look at here. 1) Atlassian Cloud. For SSO, this relies on "Atlassian Access".…