Merging Requests

Updated 1 year ago by Johnson Vo

atSpoke now has the power to merge requests! This functionality gives users the ability to merge requests to account for duplicates or multiples filed.

There are two types of requests considered during a merge: primary and secondary. The secondary request gets merged into a primary request.

Merging from a request

Navigate to a request you'd like to merge. Clicking the more button and selecting "Merge requests" will begin the process. Here you'll be able to make a request primary or secondary.

Merging from a list

Requests can also be merged from a list. Select the requests you'd like to merge, click the group of requests, and hit "Merge requests". You'll be presented with the same modal.

Merge request modal

The merge request modal will present options on which request is to be primary and secondary.

You receive a confirmation modal for the merge request.

When the requests are merged the secondary request will become locked.


What happens to followers on requests?

  • Followers of the secondary request will be added to the primary, including, requester, request assignee, and task assignees.

What happens to my chat messages?

  • The primary request chat messages will be kept with an update that links to the other requests involved in the merge.

What happens to the Request Type, Tasks, and Questions?

  • The primary will be the kept RT, while tasks for the secondary will be closed. Questions on the secondary will still be visible via the link to those requests in the updates.

What happens to the status of my secondary request?

  • The primary status will be kept but the secondary request will be locked. If the primary request is locked, then the merge will not be successful.

What about private requests?

  • Only requests of the same privacy can be merged.

Who should be notified when a request is merged?

  • We will notify followers of the primary and secondary requests as well as tasks assignee with open actions on the secondary request.

How did we do?

Powered by HelpDocs (opens in a new tab)