https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292010-05-11T08:59:07ZRedmineRedmine - Feature #5497: Assigning issues to projectshttps://www.redmine.org/issues/5497?journal_id=166382010-05-11T08:59:07ZFelix Schäfer
<ul></ul><p>Wouldn't the related issues (<em>blocks</em> and <em>follows</em> relationships) allow that?</p> Redmine - Feature #5497: Assigning issues to projectshttps://www.redmine.org/issues/5497?journal_id=166422010-05-11T10:18:27ZPedro Gutierrez
<ul></ul><p>Felix Schäfer wrote:</p>
<blockquote>
<p>Wouldn't the related issues (<em>blocks</em> and <em>follows</em> relationships) allow that?</p>
</blockquote>
<p>In fact, we find the <em>duplicates</em> relationship more helpful because it allows reflecting the state of a request.</p>
<p>But, regardless of the relationship used, we are always obliged to create two different issues to emulate this. One for the requested issue itself, another for the image of the request that remains in the client project.</p>
<p>However, I believe a single instance of the issue should be enough. The only challenge being how to reflect two views of this single instance in two projects (the client and the server)</p>