https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292009-04-02T05:20:04ZRedmineRedmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=83902009-04-02T05:20:04ZZarooba Rozruba
<ul></ul><p>Can't you split the main ticket into sub tickets?</p>
<p>So main project gets a main ticket while subprojects have more specific tickets to their domain.</p>
<p>For example;<br />'Main' project has ticket ''Integrate with system X''<br />Subproject 'Email Notification' has a ticket ''include information gleamed from system X''<br />Subproject 'Daily database cache update' has a ticket ''read data from System X''<br />Subproject 'User interface' has two tickets ''show data read from System X'' and second ticket ''on update, also update System X''</p>
<p>Finally, you setup all subproject tickets as blocking the main project ticket.</p>
<p>This way, main project ticket can not be closed until sub project tickets are closed.</p>
<hr />
<p>What I am trying to say is that, how can a ticket be assigned to many projects at once? <br />This makes little sense, unless ticket was too vague.</p>
<p>Kind regards</p>
<p>pl:Serdecznie Pozdrawiam</p> Redmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=83952009-04-02T07:47:26ZAdam Kubica
<ul></ul><p>In common case you're right.</p>
<p>Try imagine situation when three times in week you have task that affected 4 subprojects.</p>
For example (in real world it's in big scale): Main task: "Additional informations in the client data", this task affected subprojects:
<ul>
<li>subproject 1, (common: large database DDL) - new fields, tables, something</li>
<li>subproject 2, (staff/workers: backend, rails) - create new form to manage additional informations</li>
<li>subproject 3, (clients: frontend, Pylons) - display additional information</li>
<li>subproject 4, (common, some live business logic, JAVA) - make boo boo on that informations ;-p</li>
</ul>
<p>Of course, when we have that situation from time to time or/and task is enough large to split into 4 smaller task then all works fine but when task is small and situations occurs many times we must for example create 5 tickets (about 30 min work time) for job that 2-3 peoples make in 2 hours :-)</p>
<p>pl: pozdrawiam również, redmine jest świetny (ale ssie troszkę przy podprojektach).</p> Redmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=83962009-04-02T07:53:10ZAdam Kubica
<ul></ul><p>This is not ideology problem, it's time waste/task management problem in daily use.</p> Redmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=87632009-04-22T02:55:20ZZarooba Rozruba
<ul></ul><p>Then maybe a quick and easy way to create secondary related blocking issues ??</p>
<p>So someone creates a big Issue on main project.<br />and then with a single button creates sub issues in sub projects.</p>
<p>Each sub issue is flagged as an issue blocking the main project issue. ?</p> Redmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=88782009-04-28T07:25:39ZAdam Kubica
<ul></ul><p>Zarooba Rozruba wrote:</p>
<blockquote>
<p>Then maybe a quick and easy way to create secondary related blocking issues ??</p>
<p>So someone creates a big Issue on main project.<br />and then with a single button creates sub issues in sub projects.</p>
<p>Each sub issue is flagged as an issue blocking the main project issue. ?</p>
</blockquote>
<p>Yes, this is quite good solution but save some time every week :-).</p>
<p>One click, might add one related ticked in subproject (AJAX of course).</p>
<p>+1000 for that :-)</p> Redmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=90172009-05-06T14:21:00ZZarooba Rozruba
<ul></ul><p>Just noticed a related issue #443 . See if this helps.</p>
<p>Pozdrawiam</p> Redmine - Feature #3101: Ticket assigned to many subprojects.https://www.redmine.org/issues/3101?journal_id=469342013-03-18T13:48:13ZDipan Mehta
<ul></ul><p>+1. Given that now sub tasks exists - and they can be part of sub projects, I think essential thing here is that we should have a quick access UI which "create a copy as a sub ticket" and assign it to respective sub-project right away.</p>
<p>Actually the bigger challenge (and that might be useful) is that some specific fields of the main ticket controls the respective field of the sub-ticket. For example, if the customer info changes in the main ticket - the same should be reflected in this "sub-ticket". Currently, only such "controlled" fields are Start-Date Due-dates which are actually linked and cannot be changed arbitrarily. What you really want is that a set of fields, (and may be issue statuses) should also be changed once, say in main ticket and reflected everywhere.</p>