Alexey Matveev Expert

Hello, I guess you talk about next-gen projects. Features in next-gen projects are quite different from classic projects. In next-gen project you manage workflows by adding columns in the next-gen board. You can not add more rules than already available. If you want more flexibility you should move to classic projects.

Hello, The only way to migrate from a classic project to a next-gen project is to move all issues from the classic project to a next-gen project. You can read more info here: https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html

You are most welcome!

Hello, On Jira cloud it is not possible yet.

Hello, Have a look at the security levels. Security levels will let you restrict the visibility of a ticket to certain groups and users: https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html

I am not sure about Jira 4.

Hello, To make this change on a user level, a user must go to the profile and edit the Preferences option. You as a Jira administrator can not do it for the user. Or you would need a plugin, which would let you login under this user.

Hello, You could do it out of the box, if you have the Jira Service Desk installed. You could use the Jira Service Desk Automation feature. If you do not have the Jira Service Desk, then you would need a plugin like Email This Issue or Enterprise Email handler. Or you could do it with the Power Scripts add-on:…

Hello, If it is a next-gen project, then you can not associate a sub task with a next-gen project.

Hello, Join three tables: jiraissue, project and projectcategory

Try to use permission helper System -Permission Helper

Hello, You can export a filter result to a csv file or you can create a subscription to your filter. You can find more info here: https://confluence.atlassian.com/jirasoftwarecloud/working-with-search-results-764478404.html

You should go to System -> System Info. You can find server id there.

Hello, You should check the project notification scheme for this project. I guess your user is included there indirectly either by group or a role.

Hello, Switch to the Diagram mode and create a transition there:

Hello, It is possible. The user must have the Browse Projects permission. You can read about project access here: https://confluence.atlassian.com/jirakb/limit-restrict-user-s-project-access-280069544.html Also this question has been answered multiple times:…

Hello, Could you give more details what do you mean that you can not scroll through tickets?

@Vladimir Berezovski I was able to download the backup today. Atlassian did not respond. Could you try to download again?

Hello, There is no button like board settings or configure board for a next-gen board. You can not configure swimlanes for a next-gen board.

You are most welcome!

Ah, it is Trello. Sorry I did not notice. My answer is not valid for Trello.

Hello, In Cloud you can try to login under the old user and delete the filter. You can find this user in the User Management and login under this user

Hello, You would need an add-on. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=server&tab=overview You could write a post function with a code like this: #{your custom field name} = dueData - "1w"

I ve never met such a limit in an official doc. But it is there.

You are most welcome!

Hello, You should be an Agent. Log in to Jira, open the issue in question in the detail issue view and open the History tab. You will see the history for this issue. You can find more info here: https://confluence.atlassian.com/jira064/viewing-an-issue-s-change-history-720416460.html

Hello, You can not separate version creation from other admin permissions.

Hello, Summary must be less than 255 characters. You can not change it. Use the description field. Summary must be a short representation of your issue.

Hello, You need to buy an add-on for 2000 users even if it is used by 50.

Hello, It means that you made this field required in the fields configuration (project settings -> fields). Make it optional there. You need to add the Field Required validator in the reopen transition.