Alexey Matveev Expert

Hello, If you use your Jira for testing purpose, then it is fine. If you want to go to production, then you should not use the embedded database.

Hello, It is basic authentication, but instead of the password you pass API token: https://confluence.atlassian.com/cloud/api-tokens-938839638.html

Hello, You would need to use an app for it like Power Scripts or ScriptRunner. If you want to use the Power Scripts app, then your JQL query would look like this: key in silJQLExpression('length(description) > 20',<span> </span>'project = TEST and issueType = \"Bug\"')

Hello, If you want this field to be visible for users, then create a custom field and then fill it with an app like Power Scripts, ScriptRunner. If you want to use the Power Script app, then you could create a post function on the create issue transition with a code like this: #{your custom field name} = id; If you want to…

Can you paste the url in the browser and have a look, if it works or not?

That should do the trick. You can also check admin -> Permission helper to check that your user has the permission. if the permission is granted, then there could be a workflow property set in the workflow for the issue type.

Hello, Could you provide your curl request?

Solution would be different for either of them. If you execute from Jira then use a plugin like Power Scripts, ScriptRunner. If from external, then use rest api

Hello, You have to restore your Cloud instances to Server instances. Then use Configuration Manager or Project Configurator to move the project from one Jira instance to the other and then restore the required instance back to Cloud

It depends how you want to execute the transition? From an external app or Jira?

Hello, You can find a solution here: https://community.atlassian.com/t5/Confluence-questions/How-to-Configure-Confluence-server-IP-port-from-8090-to-80/qaq-p/47325

In next gen projects you create workflows via boards (you add columns). If it is not enough. Then you would need to create a classic project.

Something like Power Scripts or ScriptRunner

Hello, I am afraid, the only way is to switch to the old issue view.

Hello, Anyone with the write access can merge changes. If you do not want a person to merge to a particular branch, then go to your repo settings -> branch permissions and add a permission for a branch

Hello, You would need to add a new custom field (project settings -> issue types), not a column on the board. Columns are statuses of issues.

Hello, I believe that it is not possible in Cloud

I believe that is the reason. You can not import Jira 8 backup to Jira 7

Then you should use Jira rest api to move attachments. You could import attachments from Jira Cloud to Jira on-prem using standard export/import. But for Cloud is not available.

What are the versions of Jira from which you take a backup and to which you import the backup?

Hello, Can you check that your user is granted the Link Issues permission in the project permission scheme?

Hello, How do you try to export and import data? Do you use the backup/restore or export/import csv file feature?

Hello, Are you on Cloud? If so, it must be a next-gen project. Next-gen projects do not have the Workflows menu.

It means that the backup has the wrong format. How did you take the backup?

Hello, You would need an app for it. There are multiple apps available: Power Scripts, ScriptRunner, Automation for Jira and other apps. If you want to use the Power Scripts app, you could create a listener for the Issue Update event with a code like this: string[] subKeys = subtasks(key); for (string k in subKeys) {…

Hello @[deleted] Just write backupdata.zip. Do not provide the absolute path.

Hello, You can not put a wildcard in the beginning of a word. You would need an app for such a search.

Hello, It is not an operator. It is a wildcard character. You can find more info here: https://confluence.atlassian.com/jiracoreserver073/search-syntax-for-text-fields-861257223.html

Hello, That is right. You can not add a global issue type scheme to a next-gen project. You need to setup issue types in each next-gen project.

Hello, I think, you would need to restrict the internal comments to the Agent's group first and then move the issues. I think the group restriction must stay.