Example: Parsing text from last comment and appending it to issue's summary
I wonder if you can help me again with parsing text from an email that we receive (which shows in the comment obviously) to the end of the summary field of the the Jira ticket. An example of reply is:
Original issue summary: GCI (GI-20265) - Da Vinci Diamonds Dual - Broken- VIP 13
Last comment contains the following reply: Subject: RE: [GCI Jira] (OCC-14813) GCI (GI-20265) - Da Vinci Diamonds Dual - Broken- VIP 13 [ ref:_00D30iVRS._50014smU7L:ref ]
Desire result of the summary: [GCI Jira] (OCC-14813) GCI (GI-20265) - Da Vinci Diamonds Dual - Broken- VIP 13 [ ref:_00D30iVRS._50014smU7L:ref ]
- The invariant parts of the prefix is the summary of the original ticket
- The suffix should be everything which is within the brackets
Different example:
- Original summery: "Bonus Game Issue. Indiajaya"
- Response from IGT received as an email which contain the following Subject: "Subject: RE: [GCI Jira] (OCC-14436) Bonus Game Issue. Indiajaya [ ref:_00D30iVRS._50014slPqN:ref ]"
- Desired summary: "Bonus Game Issue. Indiajaya [ ref:_00D30iVRS._50014slPqN:ref ]
We will implement it with 2 post-functions:
Parse field for extracting data with the following configuration:
Copy a parsed text to a field with the following configuration:
Text to be parsed is:
%{00000} + (%{00000} !~ "[ ref:" AND %{00061} != null ? " [ ref:" + %{00061} + ":ref ]" : "")
Once configured, your post-functions will look like this:
Other examples of that functions
Parse field for extracting data
- Parse description for creating issue links
- Parse summary for setting "Due date"
- Parse summary for setting issue priority
- Parsing text from last comment and appending it to issue's summary
- Add all assignees of certain sub-task types to a "Multi-User Picker" custom field
- Add and remove a single or a set of items from multi valued fields
- Add current user to comment
- Add or remove request participants
- Add watchers from a part of the issue summary: "Summary_text - watcher1, watcher2, watcher3, ..."
- Assign issue based on the value of a Cascading Select custom field
- Assign issue to last user who executed a certain transition in the workflow
- Automatically close resolved sub-tasks when parent issue is closed
- Automatically reopen parent issue when one of its sub-tasks is reopened
- Calculate the time elapsed between 2 transition executions
- Close parent issue when all sub-tasks are closed
- Combine the values of several Multi-User picker fields
- Compose a parsed text including the "full name" or a user selected in a User Picker custom field
- Compose dynamic text by inserting field values in a text template
- Copy issue labels to a custom field
- Copy the value of a user property into a user picker
- Create a comment in sub-tasks when parent transitions
- Execute transition in epic
- Getting the number of selected values in a custom field of type Multi Select
- Limit the number of hours a user can log per day
- Make a sub-task's status match parent issue's current status on creation
- Make parent issue progress through its workflow
- Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress"
- Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status
- Parse Email adresses to watchers list
- Parsing text from last comment and appending it to issue's summary
- Remove versions selected in a version picker custom field
- Replace certain issue link types with different ones
- Restrict parent issue from closing if it has sub-tasks that were created during a given parent issue status
- Set a Select or Multi-Select field using regular expression to express the values to be assigned
- Set assignee depending on issue type
- Set field depending on time passed since issue creation
- Set priority for issues that have been in a certain status for longer than 24 hours
- Set security level based on groups and project roles the reporter or creator are in
- Transition linked issues in currently active sprint
- Transition only a sub-task among several ones
- Transition parent issue only when certain issue sub-task types are done
- Update Cascading Select custom field with a value of the field in parent issue
- Update checkboxes custom field if a file has been attached during a transition
- Validation on issue attachments
- Validation on MIME types of issue attachments
- Writing a comment to blocked issues when blocking issues are resolved
