Merge one request into another

If you get the same idea twice, or a small idea that belongs inside a bigger one, you can merge one request into another instead of turning it away.

Merging keeps things tidy without losing anyone. The smaller request is absorbed by the larger one and stays alive until the larger one ships.

What happens when you merge

The absorbed request is marked as Merged everywhere you look, in the list, on the board, and in its details. This makes clear it was absorbed and will still be delivered with the main request, not rejected.

Nothing is lost. The absorbed request keeps all its history visible, so you can still see who asked for it and what was discussed. To learn more, see Capture bugs and ideas and track them.

When you pick where to merge it, you only see live requests as options. Already closed or rejected requests are not offered.

What happens when the main request ships

When the main request is delivered, every request merged into it is delivered along with it. Each person who filed a request is notified when the delivery happens.

Each person gets one notice for their own part. If several requests were merged into the same main request, they collapse into one notice that points at the main request. See also Know when your request is done.

If you reopen a merged request, the merge is undone and it becomes its own request again.