Alexey Matveev Expert

Hello, When you create a board you define a filter for the board (board settings -> general -> filter). This filter selects all issues for your board. Kindly check that the four issues are selected by the filter for your board.

Hello, the Time Tracking field actually consists of two fields: Original Estimate and Remaining Estimate, that is why you should map these two fields during csv import. https://confluence.atlassian.com/adminjiraserver071/importing-data-from-csv-802592885.html

Hello, You should use the opsbar-sequence property. You can find more info here: https://confluence.atlassian.com/adminjiraserver071/advanced-workflow-configuration-802592741.html Go to the To change the order of transition buttons part

You should use the WithPlugin annotation. You should find the required by you service/manager and inject it with the PluginModule annotation: @PluginModule YourService

You are very much welcome!

Hello, I guess, the filter, which is used for the board is not shared with you. That is why you do not have access to the board. Your user should be added to a group with which the board filter is shared.

Hello, The only way to let a user to edit a dashboard is to make this user the owner of the dashboard.

Try to type like this: issueFunction in hasComments(3) In Scriptrunner for Jira Server you need to use the issueFunction in and then your function.

Hello, How to make the query? Rest Api?

If you grant the Browse Issues permission to Assignee (there is such a choice). Then only the Assignee of a ticket will be able to see the issue. If you have a role, which also has to see all issues, you can grant this role the Browse Issues permission as well.

Hello, There is the Service Desk Api. You can find some info here on how to use it in ScriptRunner: https://scriptrunner.adaptavist.com/latest/jira/recipes/misc/jira-service-desk.html You can find Java doc on the Service Desk Api here: https://docs.atlassian.com/jira-servicedesk/3.9.1/ Have a look at the PortalService…

You are welcome!

Hello, You define issues, which are visible in a board by a JQL query (board settings -> general -> filter). You can add a special status (On hold for example) and when you write the JQL for the filter, you do not include the On hold status for selection (status <> "On hold"). In this case you can move an issue to the On…

I confused the create issue action with the create linked issue. You should use the Hide UI element built -in. https://scriptrunner.adaptavist.com/5.4.7/jira/fragments/HideUIElement.html You should add such a module. Choose the create-linked-issue-item in the Hide What field. Then write a condition in the Condition field.…

Hello, I guess, your question means that this group of users has also access to projects, to which they do not have to have access. It means that the users in the group are also included in other groups or roles and these groups or roles have the Browse Issues permission in the projects where the users should not see…

Hello, After you counted the time period between two transitions, how do you want to show it? Do you need it for an external application or somewhere in Jira? If you need it for an external application, then you can use Jira Rest Api. If you need it in Jira internally, then you can use Jira Java Api.

Hello, You should use ScriptRunner behaviours 1. Create a behaviour and add the cascading custom field to the behaviour. 2. Write a script for the added cascading field. Your script should be like this: def cascField = getFieldByName("cascading field name") def hiddenField = getFieldByName("name of your hidden field") if…

Hello, Here is how you can find a email address in the Groovy language: https://compoundthinking.wordpress.com/2012/06/04/how-to-validate-email-address-with-regular-expression-in-groovy/ After you received the address you can save it in a custom field like this:…

Ah, I see. Then I guess the answer of @Yogesh Mude is correct :)

You are welcome! Try this solution in a test environment first. If it works, kindly accept my answer. In this case other people with similair question will be able to find this answer.

Hello, It is by design. When you open the Edit issue screen you can only add new attachments. You can not see or modify attachments, which are already attached to the issue. You can not change this behaviour of the Edit issue screen. All you can do to write your own plugin or look for a plugin in the Atlassian marketplace,…

Hello, Where do you write this script? What is the status variable?

Your script would look like this. You can run it in the ScriptConsole of the ScriptRunner plugin. Kindly check the script first in a test environment. import com.atlassian.jira.issue.fields.CustomField import com.atlassian.jira.issue.fields.config.FieldConfig import com.atlassian.jira.issue.context.IssueContextImpl import…

Hello, It is impossible to change a custom field type through the UI interface. The safest way is to create a new field and copy all values from the old field to the new field using an add-on like Power Scripts or ScriptRunner.

Hello, For a servlet you can check if a user is logged in and if not, then redirect to the login page. You can find an example here: https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-make-a-Servlet-plugin-module-accessible-only-after-login/qaq-p/548510 Your REST endpoint must require login.…

Hello, Nothing will happen to the issues. Archived means to hide an old version from the Change Log reports, and in the Jira User Interface. You can find more info here: https://confluence.atlassian.com/adminjiraserver071/managing-versions-802592484.html

Hello, You can not set multiple assignees to an issue. You can create a Jira user for a group of users and assign a ticket to this Jira user. You can handle notifications with the project notification scheme. You can set users in the project notification scheme, who have to receive notifications on certain events.

Hello, ScripRunner for Cloud and Server is different. You name features for Jira Cloud. These feature are not available for Jira Server.

You can not enforce password change in Jira. Kindly read the following thread: https://community.atlassian.com/t5/Jira-questions/Force-users-to-change-password/qaq-p/43047

Try to change the line to: def estField = ComponentAccessor.getCustomFieldManager().getCustomFieldObject(11401L)