Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Jira automation

Rajan Dangol
Contributor
November 28, 2024

Hi,

 

 

I have a project with two request types: one for connection issues and another for testing. A connection issue is classified as an incident, while testing is classified as a problem. I've created a custom field to track when a request moves from one type to another—for example, when an incident turns out to be a problem, and the field needs to be updated accordingly.

How can I make this amendment? It would be easier if the request moved between projects, but since it's a change in request type within the same project, tracking it is more challenging.

Do you have any suggestions?

 

Thanks,

Rajan

1 answer

1 vote
Harshit Grover November 28, 2024

Hi @Rajan Dangol ,

You can use Automation Rule within your project settings to achieve this workaround :

  1. Custom Field Setup: You've already created a custom field to track the transition. Ensure it is of a type that can hold values like "Incident" and "Problem" (e.g., a single-select or text field).

  2. Update the Workflow: Make sure the workflows for both request types (Incident and Problem) have clear transitions. For example, when an Incident is reclassified as a Problem, there should be a logical state transition (e.g., "Reclassified").

  3. Automation Rule to Track Request Type Changes:

    • Go to Project Settings > Automation > Create Rule.
    • Configure a rule as follows:
      • Trigger: Field value changed for the "Request Type" field.
      • Condition (optional): Use an "If" condition to check the old and new values of the "Request Type" field to ensure the change is meaningful (e.g., Incident to Problem or vice versa).
      • Action: Update the custom field with the new request type or a status message indicating the change (e.g., "Changed from Incident to Problem").
      • Optional Action: Add a comment or notify the assignee/others about the reclassification.
  4. History Tracking:

    • Jira automatically tracks field changes in the History tab of the issue. If you need this to be more visible, consider creating an audit log using the same automation rule to add a comment with the transition details.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events