Allow multiple resolving items per issue

[#1]

Currently only one resolving items is allowed per issue.

Most of the time we have more then one action to address an issue, so limit of "1" forces us to create weird workarounds such us creating a resolving task, with many subtasks, or a task with many issues, but then reporting on progress becomes cumbersome.

If issue could have many resolving items, it would become easier to report by filtering items that have  "this resolves" relationship defined and group by it.

[#2]

Surely this would be confusing no? Having multiple linked resolving projects and not knowing which one resolved which part of the original request?

If we have multiple actions, we simply convert the request/issue into a project, then assign various tasks for the multiple actions. Would that not work for you?

[#3]

RossHa: Thanks for feedback.

If tracking several items to close an issue is confusing, then setting up a new project and tracking the same several items separately would be even more confusing. It can be done, but it doesn't seem the most efficient way, not to mention the added overhead of creating and maintaining new project. I would pick a project as resolving item for a big problem demanding a separate team, budget, schedule and WBS. Just missing an easy way of tracking completion of issues that require "A,B and C" to be done. 

[#4]

We are exploring a pilot to use one request issue for multiple resolving projects. The idea is for the Stakeholder to submit a full campaign brief that multiple project managers will leverage for their specialized projects.