Alexey Matveev Expert

You are welcome! If my answer helped you, kindly accept my answer.

You would need to create custom field, which would return the order of an issue and then sort by this field. You can create such custom fields with plugins like Power Custom Fields Premium or ScriptRunner.

Hello, Go to the Issue Navigator and write a JQL query like thils "Epic Link" = EPIC-1 Then use the export option.

As you can see, some fields are not associated to the other issue type. I personally never had 2 Epic issue types. I had it once in a system and had the same problems like you. Then I got rid of the one of the Epic issue types and everything worked fine. Jira Software is not supposed to work with 2 Epic Issue types. You…

Hello, What is an archived project?

Hello, You would need to introduce security levels: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

Hello, What is POV? You can use the import issues from csv file feature: https://confluence.atlassian.com/adminjiraserver074/importing-data-from-csv-881683854.html

Hello, Rest endpoint does not return any velocity templates. You should use a servlet module instead.

You should leave only one Epic type. Find the Epic type, to which the Epic Name is associated, then convert issues of the other Epic issue type to this one. Try to convert a single issue first and have a look that all Epic links stayed untouched. Then you can use the Bulk Move feature.

Hello, You would need a plugin for it. There are 2 way to implement it with plugins: 1. You can use plugins like Power Scripts or ScriptRunner to implement a validator for the field. If you want to use the Power Script app, then the code for validator would look like this: string str = #{Your custom field name}; if (#{Your…

If plugins have such automated tasks then the fields will be locked after start. For Jira Software it will not be locked. At least I already unlocked this field and on startup this field stayed unlocked. The Epic Name field by default is available only for Epics. You should not add it to other issue type, it can influence…

Hello, Have a look at this post: https://community.atlassian.com/t5/Answers-Developer-Questions/Create-issue-via-REST-API-useing-Java/qaq-p/518478

Hello, To sort tickets you should use the ORDER BY close. For example, to sort issue by the creation date, you would write a JQL like this: project = PROJECT order by created

Hello, I believe that you can see the link in boards:

Hello, There are no special permissions to unlock a field. The only way to do it through the database. Database access is only allowed on Server, which means that you can not unlock a field on Cloud. And if a field is locked, it means that the developer of the app, who added the field, decided, that this field should never…

Hello, You can export issues, if you go to the Issue Navigator, type a JQL query and then use the Export option. You can do it without admin permissions. But you can import without admin permissions only if you are on Cloud. The Import option is available for non-admins in Cloud. You can find more info here:…

Hello, You can configure field configuration scheme so that every issue type would have its own field configuration. Have a look at this doc: https://confluence.atlassian.com/adminjiraserver/associating-field-behavior-with-issue-types-938847262.html

If you delete a project, then you can create a new project with the key of the old project.

You should see tasks on the board. How do you create tasks? I have not found an option to create tasks from the roadmap.

Most of them were in the same location.

There are no rules of thumbs. I had experience in working 3000 agent with one project, which had about 2 million issues. The performance was fine. The number of issues will influence the performance. 

Do you create epics or stories?

400 agents for a project is fine. It all depends on the number of issues, custom fields and so on. Measure your performance. If the performance is ok for you, then it is fine. If not, then think about moving to Data Center

Hello, Board settings are not available for next-gen boards.

Hello, Have a look at the federating instances: https://confluence.atlassian.com/adminjiraserver/federating-jira-managing-multiple-instances-961257360.html

Because, Atlassian does not let users work with the database in Cloud. In Server it is also not the best practice.

Hello, You can copy the url, when you open the dashboard, and send this url to the group. But you still need to share the dashboard with the group so that users in the group could access your link.

Hello, You can also delete and then create the project again.

Hello, There is no recommendation, which I know of. You should have as many agents as you need.

Hello, Are you on Cloud or Server? If you are on Cloud and you are using the New Issue View then there is only one tab available at a time, you need to switch between tabs: