Alexey Matveev Expert

Hello, Just remove this custom field from the edit screen for this issue type (project settings -> screens)

Hello, Are you on Jira Cloud or Server? Basically all changes are done by Jira Administrators.

Hello, You could use Jira Rest Api for it: https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/?_ga=2.10711155.675557620.1538152808-65270402.1526147845#api/2/issue-createIssues

You are welcome!

It is not possible.

Hello, You would need to setup your undo tasks in your undo tranistion. For example, if you moved an issue from the New status to In progress status and created a sub-taks, then you need to delete this sub-task if you Undo this operation (move from In progress to New). You should implement this logic yourself. Jira can not…

Though it will be visible only in the old issue view. For the new issue view it will not take place. You can see the following ticket: https://jira.atlassian.com/browse/JRACLOUD-68967

Open the view screen for the issue type of the issues and reoder fields (project settings -> screens)

Hello, Notification schemes can be managed only by Jira administrators.

Hello, It is possible. You can find more info here: https://confluence.atlassian.com/servicedeskcloud/adding-customers-852724126.html

You do not need to confiugre anything. Just download the plugin, install it as an add-on and then go to the Issue Navigator and type the JQL query: You can download it from here: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=server&tab=overview

Hello, You would need a plugin. Kindly have a look at this plugin: https://marketplace.atlassian.com/apps/1215700/notifications-for-jira?hosting=server&tab=overview

Hello, You can not change the order of the custom fields this way. All you can do is reorder custom fields with the web panel, where they are shown.

Hello, As far as I understand the JQL query with the originalEstimate is EMPTY returns tickets with the originalEstimate field set to a value. If so, reindex your Jira.

Hello, You can not write such a JQL query out of the box. 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 wirte a JQL query like this: 'reporter ==…

Hello, What status did you map to the Moved to TST column in Kanban? If you add a column, you should map a status to it. If this status does not exist, you should add this status to the worflow of the issue and create a transition from the status in the previous column to the new one.

That is right. You can do it with the bulk edit functionality. You should write a JQL like this: yourcustomfield is empty Then bulk edit your custom field with the defult value. You can find more info about bulk edit here:…

You could make a custom field: Email Sent as a text field or number (do not put it on a screen). Then in the same trigger fill this field with value 1. Then in condition you would check the status and this field is not equal to 1.

If you restart your virtual server, then both of your services will be up.

Hello, It will work just fine as long as you have enough resources. Confluence will run on 8090 port and Jira will run on 8080.

Hello, You can do it with the Service Desk Automation. Create the Status Changed trigger, create JQL condition that checks in what status the issue is, then you add the Send email action. You can find more info about Jira Service Desk automation here:…

Hello, You should have a look at the log in the SQL Server side. But my guess is that SQL Server wants Windows authentication, but you connect with sql server authentication mode.

Hello, Do I understand correctly that you have Jira Service Desk? If so, you can do it with the Service Desk automation: https://confluence.atlassian.com/servicedeskcloud/automating-your-service-desk-732528900.html

Hello, Open an issue and go to the History tab: https://confluence.atlassian.com/jira064/viewing-an-issue-s-change-history-720416460.html

Boards do not contain issues. Issues are selected to boards by JQL queries. That is why if you create an issue from the board interface, it will go to all boards, which select it by their filters. That is why you need to set some field in the created issue (a group, an assignee, any other flag) so that you could later…

It will not work because you do not have such users as assigneescrum and assigneekanban. How do you understand that an issue belongs to a scrum board or to a kanban board?

Hello, I think it would be like this: struct property { string property; string value; } struct properties { property [] properties; } struct returnData { string status; string issueId; } property [] propertyArray; property p; properties newIssue; p.property = "short_description"; p.value = "Description Goes Here";…

You are welcome! :) 

Ok. Got it. Your JQL filter is the same for both boards. Here it is: project = HT order by Rank asc (it is seen on your screenshot). How can you understand if an issue must be shown in the kanban backlog or in the scrum backlog. For example, if you can differ it by assignees then you should change this query like this: For…

IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Componentbug, "First issue", v1, , , Component1,bug, "Second issue", v2, , , Component1, Component2bug, "Third issue", v1, v2, v3, Component1,