Alexey Matveev Expert

Hello, First of all you need to define what distribution of Jira you want. I guess if you want to work with Incidents, then you need Jira Service Desk If you want these150 users work in the Jira interface, not in Portal, then you will need: For Jira Server/Data Center 250 user license. For Jira Cloud 150 user license.

Can you open cog wheel -> Issues?

Hello, The roadmap feature is applied only to next-gen projects and only to epics.

Hello, Are you on Jira Server or Jira Cloud?

Yes, the old tickets will have these fields but they will be empty for these issues.

What I meant is to make a timer in your js. It will not make updates work longer. The logic is the same like in EditableDetailsViewReloader.js. If you could attach your panel to the same reloader then it would be good.

Hello, You can use the bulk edit feature. Go to Issue navigator and search all items where your field is empty: yourfield is Empty and project = PROJ Then use the bulk edit feature to set a value for this field for all issues. You can read more info about bulk edit here:…

Hello, You could check if your panel updates or not by Jira itself. If it is not updated, then you would need to implement the update feature in your panel code (You could use a timer to check, if something changed in the issue).

Hello, It means that the Component field does not fit your requirements. You should use a single or multi select custom field. In this case all values will be consistent in different projects.

You are welcome!

Hello, I also can not create multiple boards for an next-gen project. I guess, it is not possible.

@Christos Moysiadis You are welcome!

Hello, You need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation You could create the following condition: if (isNull(assignee)) { return false; } return true; You can read more about conditions here:…

To tell you the truth I have a rule never to do any inserts or updates in the Jira database. I always use Jira Api to change anything in Jira. I think it is feasible the way you want to do it. But you never know what can go wrong because it is not the right way to do. Everything must be done through Jira Api. Anyway test…

You are welcome!

Hello, You should use this Rest Api to get issue history with the changelog option: https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/?_ga=2.63710255.1405038281.1539585246-492126670.1535639244#api/2/issue-getIssue

Hello, Roadmap is only available for next-gen projects. You have a classic project. You can use the roadmap in a classic project.

It will make your data in the database inconsistent. You will delete just components, but all references to this components from issues will stay. I would advise not to do it via SQL quieries.

Hello, If you want an out of the box solution, you can use the Jira Rest Api: 1. Get all components by https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/#api/2/component-getComponentRelatedIssues 2. Delete components by https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/#api/2/component-delete

Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a validator like this: if (dueDate < currentDate() ) { return false, "Date must greater or equal to the…

I attached a screenshot:

7.12.3 fixes bugs in 7.12.0 and provides new features for 7.11.2. Usually versions after 2 are stable enough. I would install 7.12.3

Hello, You can create a board. Then go to board settings -> swimlanes and choose stories. Then in the active sprint view, you will be able to see stories and sub-tasks under these stories. I think it is the best you can get out of the box Jira.

Hello, The latest stable version of Jira Software is 7.12.3

Hello, It means that you are on Jira Cloud and all your projects are next-gen projects. You can not associate issue type scheme to next-gen projects. You should create a classic project if you need to do it. In Next-gen projects, you should go to project settings -> Issue Types and add a new issue type there.

Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a condition like this: string selectedGroup = #{Your Group Picker Name}; if (isNotNull(selectedGroup) &&…

Hello, Are you on Server or Cloud? Next-gen projects are only available for Jira Cloud.

Hello, Go to board settings - > Columns and have a look, what status is connected to backlog and what status is connected to the To Do column. Make sure that there is a transition in the workflow, which leads from the status in the backlog to the status in the To do column.

Hello, It is a next-gen project. You can not assign a new permission scheme for next-gen projects. You should create a classic project.

Hello, Are you sure that you can see this custom field in the issue view screen for an issue in the project, which does not have this custom field? If you can not see, use the Where is my field option in the issue view screen in the Admin menu.