Nic Brough -Adaptavist- Expert

Comments are not a field, they are a discussion and place to make informative updates. You don't need comments on issue creation - whatever someone is thinking might go in a comment is perfectly valid to put in the original description. Think of it this way - would you respond to your own statement in a real spoken…

"Sections" have gone away on Cloud - these are now "layouts" which don't have one column (that's just body text now) and cannot be re-arranged.

Please, STOP SHOUTING - it's rude and hard to read. Trello does not have functions to do this. You will need to add one of the power-ups that can do this.

See above for why you can't do this, and won't be able to in the future

Only way I know to do this is to raise a support request with Atlassian and ask. They usually respond very quickly with either "it is in this area" or "it is in this area, do you need to move it to another"? https://support.atlassian.com/contact to get started.

What do you want from your "integration"? The word tells us you want two systems to talk to each other, but nothing more of any use in answering the question.

The next step is to look at the "environment". If the "start confluence" script works when run on the command line, but the service fails, then what's the difference in the environment those two run in?

It's really not that simple. I would stop trying to read the database and try to do whatever you are trying to do via supported routes. Could you explain what you are trying to report on? And why you're not using the REST API to do it?

In principle, no. Jira does not do field level security (because hiding bits of issues leads to confusion and doubt) You can do the "only set by" thing though. Edit the workflow, creating transitions that are protected by "manager only" conditions that then go through screens that include the protected fields. Then remove…

The simple answer is to go to "find new apps" in your system, select Script Runner, install it, and follow through to purchase. Like almost all apps for Jira. For your more detailed questions though: The disclaimer bit: ScriptRunner allows you to write whatever you want, including stuff that could get sent to Adaptavist.…

I am not sure what you are looking for there.

Go to the project admin section for that project, and check what the permissions are.

Nope. It makes some difference, of course, any processing change does, but nothing you will really notice. Hiding a field in a field configuration does not have any significant effect. If you want to improve performance of custom fields, you will find it a thousand times more effective to reduce a field's context. (Or best…

Ok, why? Why would that be better than what we have now? How would you suggest your average user decides whether to use a folder or a page hierarchy? Please, explain the benefits?

The link is to the previous community site. A generic event is the event fired by default when Jira has not been told to fire a better one. They're no different to any other event, other than in name.

I apologise, you are absolutely right. The last time I did a migration myself, it was a 6.4ish version, and more importantly, had significant customisations. Including something that deliberately set the page author on import. That is an explanation of why I'm wrong, but not an excuse, because I should have checked before…

Not changed, I've not found a reason to look for this, so I've not found any code that might do it.

You can't use those in this gadget. You'll need to use one of the field types that can be grouped (select-type fields such as radiobuttons, versions, users, select lists etc)

The system does not record that information. Unless you are importing from a system with different users, in which cases, the pages will be owned by the importer, rather than the author who isn't in the target system

I'm afraid there is nothing that would let you do this. It might even be easiest to take a backup of the Cloud system, download that and then parse the XML for the workflows, and then the XML workflow for the post-function, validator, conditions etc.

The reporter is limited to people who can create issues in the project in the background, plus customers if it's a JSD project. I suspect your permission scheme is open, allowing everyone create permission.

To add a field into the date/time section, you don't need to do anything more than add a field that is of a type that panel draws into itself. Jira will do it automatically. So, either a date or a date/time field. Making a field required is a separate thing - change the filed configuration for the project to make it…

There's no way to do this at the moment, sorry. A version is a project-level artifact and can only exist in one project. If you have a separate "scrum project", it is not going to have versions from other projects (even if you duplicate them with the same name, you'll find the versions are separate entities in different…

The list of types of links is set by your administrators. There's a default list in a new Jira install, but you can add to, remove or edit the whole list. I would guess that your admins on your older Jira had set up a link type called something like "dependency" and then labelled the directions as "predecessor" and…

As soon as you run a filter like that, you're outside the project context, so it's showing "all"

But flickering on-screen for a sec and then disappearing does suggest javascript (including Behaviours if you were on Server), so I would want to check exactly what you see when you go into "configure" - is the field enabled there? Does it appear if you select it?

This suggests your "business unit" field is not of a type you can list. From the name, I would guess it is a free-text field.

I'm afraid "sections" have been removed in the new editor. We can't do them any more. The layouts are a weaker version of them, supporting 2 or 3 columns and without any move function. (I want sections back - the power they had for easy reformatting was far better than layouts)

Behaviours is a module within the ScriptRunner app that can inject javascript that modifies the front-end of Jira on the client side. You do not have it though - it does not (yet) work for Cloud.

Is "root" a valid admin user in Jira? (Standard advice here though - do NOT do this automatically, you should not need to do it)