The problem
Were you ever wondering why you queues looks so confusing?
...
- Hide Summary in Edit Fields configuration in Service Desk Project settings
- As you have to provide some predefined value, use for example "temp_value", as this text will exist for hundredth of second, it doesn't really matter what you will use
- Enter the Workflow configuration
- Select Create transition (that first one with circle at the beginning)
- Select Post Functions
- Click Add Post Function
- Select "Set field value (JMWE add-on)" and configure in following way
- Field: Summary
- Value Type: Constant or Groovy Template
Value:
Code Block language groovy <%= issue.get("reporter")?.displayName %> | <%= issue.get("customfield_13918")?.name %> | <%= issue.get("customfield_14370")?.get(null)?.value %>- Leave all other checkboxes unchecked
- Set the post-function order JUST before the re-index an issue step!
- JMWE will warn you, that this should be before Create this issue originally, but trust me. It wont work
- JMWE will warn you, that this should be before Create this issue originally, but trust me. It wont work
Result
Instead of having randomly by user filled Summary
...
you will got results similar to this one:
| Tip | ||
|---|---|---|
| ||
You can use different naming rules by using "Run this post-function only if the following condition is true:" In my case, I do have different Summary scripts for Debit vs. Credit cards, whose are using different custom field to be put into the Summary. Conditions are based on checking true|false if the value for Debit, or the value for Credit is present. This will of course result into two post functions with two conditional executing. |