confluence.atlassian.com Open in urlscan Pro
108.138.36.78  Public Scan

Submitted URL: http://confluence.atlassian.com/display/SDKB/Replacing+legacy+automatic+transitions+with+automation+rules
Effective URL: https://confluence.atlassian.com/jirakb/how-to-fix-this-service-project-may-not-work-as-expected-error-777027034.html
Submission: On October 30 via api from FR — Scanned from FR

Form analysis 1 forms found in the DOM

<form>
  <radiogroup>
    <div class="reason-radio-box">
      <label><input type="radio" name="was-this-helpful-no-reason" value="It wasn't accurate"> It wasn't accurate</label>
    </div>
    <div class="reason-radio-box">
      <label><input type="radio" name="was-this-helpful-no-reason" value="It wasn't clear"> It wasn't clear</label>
    </div>
    <div class="reason-radio-box">
      <label><input type="radio" name="was-this-helpful-no-reason" value="It wasn't relevant"> It wasn't relevant</label>
    </div>
  </radiogroup>
</form>

Text Content

Products


JIRA SOFTWARE SUPPORT

 * Get started
 * Documentation
 * Knowledge base
 * Resources

 * Search
 * Log in
 *  * View account
    * View requests
    * Log out

 * ...


GET STARTED


KNOWLEDGE BASE


PRODUCTS


 * JIRA SOFTWARE
   
   Project and issue tracking


 * JIRA SERVICE MANAGEMENT
   
   Service management and customer support


 * JIRA WORK MANAGEMENT
   
   Manage any business project


 * CONFLUENCE
   
   Document collaboration


 * BITBUCKET
   
   Git code management

See all


RESOURCES


 * DOCUMENTATION
   
   Usage and admin help


 * COMMUNITY
   
   Answers, support, and inspiration


 * SYSTEM STATUS
   
   Cloud services health


 * SUGGESTIONS AND BUGS
   
   Feature suggestions and bug reports


 * MARKETPLACE
   
   Product apps


 * BILLING AND LICENSING
   
   Frequently asked questions

 * Log out
 * Log in to account
 * Contact support
 * Training & Certification
 * Cloud Migration Center
 * GDPR guides
 * Enterprise services
 * Atlassian partners
 * Developers
 * User groups
 * Automation for Jira
 * Atlassian.com

 * PAGE

 * View in Confluence
 * Edit Page

 * VIEWPORT

 * Manage Viewport

 * CONFLUENCE

 * Dashboard
 * Space Directory
 * People Directory

 * Atlassian Support
 * JIRA Knowledge Base




HOW TO FIX THIS SERVICE PROJECT MAY NOT WORK AS EXPECTED ERROR

RELATED CONTENT

 * Possible causes to error: "You don’t have permission to transition this
   issue/ticket"
 * Error when transitioning an issue to a known status with Jira Automation
 * Status not changing when comment is added to the ticket
 * How to automatically change the assignee when transitioning the workflow
 * Allow Customers to reopen issues only within X days from resolution
 * Restrict Transition Options for Issues in On Hold and Pending with Requester
   Status
 * Using the request-channel-type property on filters
 * Workflows Troubleshooting
 * How to automatically update Jira Service Management Approvals when Assets
   approvers change
 * No customer email notification received from Subtask in Jira Service
   Management project

STILL NEED HELP?

The Atlassian Community is here for you.

Ask the community


PROBLEM

When viewing your Jira Service Management project, you see the following
configuration error message:

This service project may not work as expected.

When you click the message, you see the following details: 

Wait! We need to talk...It looks like you haven't yet moved to our new and
improved automation rules. We need to disable your existing issue transitions to
make sure your service project runs smoothly. As a project admin, you can create
a "Transition on comment" automation rule here. When you're ready, click below
to disable your previous issue transitions and remove this error message.


CAUSE

The Jira Service Management project workflow has been modified to
include customized issue transitions that are no longer supported. When
modifying your workflow, you or a previous Jira administrator likely made the
following changes: 

 1. Configured a customer to agent transition by adding the sd.step.key property
    key and sdWFCustomer property value to a step, and then adding
    the sd.action.key property key and sdWFCustomerToWFSupport property value to
    a transition (or action) from that step to another step.
 2. Configured an agent to customer transition by adding
    the sd.step.key property key and sdWFSupport property value to a step, and
    then adding the sd.action.key property key
    and sdWFSupportToWFCustomer property value to a transition (or action) from
    that step to another step.

Legacy transitions such as those referenced above have been replaced by
automation rules, which are much easier for you to configure and manage in each
service project. The configuration error message will appear in your service
project until these legacy issue transitions are disabled. 


RESOLUTION

CHECK YOUR JIRA SERVICE MANAGEMENT PROJECT WORKFLOW PROPERTIES

We recommend that you view the project's workflow (which can be found by going
to  > Issues > Workflows) and examine the properties for each workflow step:

 * If one of your workflow steps has the sdWFCustomer property value, see if you
   can find a linked transition with the sdWFCustomerToSupport property. If you
   find one, you have been using the customer to agent transition in your
   project. You will need to create a corresponding automation rule (e.g. "When
   issue commented -> If [status of step] -> Perform [transition]").
 * If one of your workflow steps has the sdWFSupport property value, see if you
   can find a linked transition with the sdWFSupportToWFCustomer property. If
   you find one, you have been using the agent to customer transition in your
   project. You will need to create a corresponding automation rule (e.g. "When
   issue commented -> If [status of step] -> Perform [transition]").

CREATE A NEW AUTOMATION RULE

To mimic this legacy transition behaviour, you will need to create a new
Transition on Comment automation rule:

 1. Open your service project and proceed to Settings > Automation.

 2. Select New rule.

 3. Choose Transition on Comment from the list of automation rules. The default
    rule will mimic both the customer to agent and agent to customer
    transitions. If you only want to use one of the transitions, you can simply
    delete the IF condition that doesn't fit your needs. Note that the IF box
    with the "and user is a customer" condition applies to the customer to agent
    transition; the IF box with the "and user is not a customer" condition
    applies to the agent to customer transition:
    . 

 4. Once you have created the needed Transition on Comment rule, free to check
    out the other automation rule options to help increase your team's
    efficiency with additional service project processes. 

DISABLE REMAINING LEGACY TRANSITIONS

Now that you've created an automation rule to replace legacy transitions, you
can resolve this error message.

 1. Open the error message.
 2. Select Disable old transitions. The legacy transitions will be disabled and
    the configuration error message will be removed.



Last modified on Nov 23, 2020


Was this helpful?

Yes
No
It wasn't accurate
It wasn't clear
It wasn't relevant
Provide feedback about this article

RELATED CONTENT

 * Possible causes to error: "You don’t have permission to transition this
   issue/ticket"
 * Error when transitioning an issue to a known status with Jira Automation
 * Status not changing when comment is added to the ticket
 * How to automatically change the assignee when transitioning the workflow
 * Allow Customers to reopen issues only within X days from resolution
 * Restrict Transition Options for Issues in On Hold and Pending with Requester
   Status
 * Using the request-channel-type property on filters
 * Workflows Troubleshooting
 * How to automatically update Jira Service Management Approvals when Assets
   approvers change
 * No customer email notification received from Subtask in Jira Service
   Management project

Powered by Confluence and Scroll Viewport.
Atlassian
 * Your Privacy Choices
 * Privacy Policy
 * Terms of Use
 * Security
 * © 2024 Atlassian



This site uses cookies to improve your browsing experience, perform analytics
and research, and conduct advertising. To change your preferences, click Manage
preferences. Otherwise, clicking Accept all cookies indicates you agree to our
use of cookies on your device. Clicking Reject all cookies means you do not
agree to our use of non-strictly necessary cookies on your device.Atlassian
Cookies and Tracking Notice
Manage preferences Reject all cookies Accept all cookies



MANAGE PREFERENCES

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Accept all

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They are based on uniquely identifying your
browser and internet device. If you do not allow these cookies, you will
experience less targeted advertising.

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. If you do not
allow these cookies we will not know when you have visited our site, and will
not be able to monitor its performance.

Back Button


COOKIE LIST



Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Reject all Confirm my choices