I have created request types, have fields populated, some hidden, some required to choose, and based on a combination of field options chosen, I have a Project Automation rule to set two fields, one of them being the Customer Request Type field, which is set by Jira Service Management, but is also able to be changed.
For it to initially work, I had to create "dummy" request types with Request Type names to match the eventual output desired based on the rule. I did that, no problem. When that was complete, I tested the rule and it succeeded. When I delete my dummy request types, the rule fails. Even when I re-create them, the rule still fails. There should be nothing that is causing the rule to fail, but it is.
Is there something I'm missing?
I think I stumbled upon the process that makes it work. It's pretty clunky, but it works.
Like I said, clunky, but it works now. Likely a one-off situation, but is someone does happen to need it, and stumbles across this, at least it's documented.
Why don't you use a separate customfield instead of changing the customer request type?
My understanding is that customer request types could be different issue types with different fields and workflows and changing the value will cause issues.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Customer Request Type field is being used for metrics, and we have a LOT using it. It would be a HUGE undertaking to change that, but thank you for the response and seggestion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.