...
No | Use Cases | Version |
|---|---|---|
1 | As a developer, I have to transition the subtasks on the issue to the same status as it’s parent task when parent task is transitioned | Cloud |
2 | As a developer, I have to prompt (ask) the user if they want to close the parent ticket when all sub-tasks under the ticket are done | Cloud |
3 | As a developer, I have to change the fix version field of sub-tasks based on parent task’s fix version field value on update event | Server / Cloud |
4 | As a developer, I have to set a default value for fix version field | Server |
5 | As a developer, I have to add the custom field value while changing the status to the particular screen: post-function | Server |
6 | As a developer, I have to change the status of particular issue on update event | Server / Cloud |
7 | As a developer, I have to set a default value for fix version field for a particular issue type | Server |
8 | As a developer, I have to get the linked issues of particular issue | Server / Cloud |
9 | As a developer, I have to add a comment to the linked issue and the main issue | Server |
10 | As a developer, I have to get all the sub tasks on a issue and their issue keys | Server / Cloud |
11 | As a developer, I have to hide the custom fields on create screen if the user is not a project admin | Server - Behaviors |
12 | As a developer, I have to create issues of particular issue type when a classic project is created | Cloud |
13 | As a developer, I have to deactivate users if they are inactive for long time and doesn't belong to a group(s) | Server |
Post Migration Script changes in cloud:
Once the Jira or Confluence migration takes place from Server to Cloud we have to identify the scripts that were running on Server and convert them to be compatible for Cloud. The scripts can be in various different apps such as Scriptrunner, JSU, JMWE etc., The syntax might differ a bit but the core logic remains the same. As per the mentioned apps above, the Cloud syntax is not very different from the Server. Below are few examples on how the scripts can be converted from Server to Cloud. The scripts can be written for various scenarios such as listeners, workflow conditions, validators, post functions etc., but majorly it will be on workflows.
Examples:
No | App | Use Case | Server code | Cloud code | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Adaptivist Scriptrunner for Jira | Must not be able transition the issue unless condition is true or it returns a truthy value |
|
| ||||||||||
2 | Adaptivist Scriptrunner for Jira | Transition must be blocked unless it returns a truthy value |
|
|
Reference Links:
Jira Expression Types: https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference/#user
Scriptrunner Example Conditions: https://docs.adaptavist.com/sr4jc/latest/features/workflow-extensions/conditions/example-conditions