Vote #72157
未完了Automatic update of related issues
0%
説明
I am looking for a solution that would allow to create a relationships between the issues that would update the one of the issues automatically.
For example. We have a issue A and issue B. These issues are connected with a proper relationship(but but I am not concerned about duplicated by, because it will only close one of the issues). Now if I change any property of a issue A such as progress bar %Done or Priority or Due date or start date or status, issue B will automatically change. And vice versa
I am working on a Redmine version 2.0.1
I'll be very grateful for Your help.
journals
This is already available via issues follows/recedes relationship type, please read [[RedmineIssues#Related-issues|RedmineIssues#Related-issues]] and issue subtasking (documentation at [[RedmineIssues#Subtasks|RedmineIssues#Subtasks]] is not accurate about this feature).
--------------------------------------------------------------------------------
I know that this is possible in one project. I thought about the connections between issues in different projects?
--------------------------------------------------------------------------------
Michał Chełmiński wrote:
>I know that this is possible in one project. I thought about the connections between issues in different projects?
After changing anything in the issue A, Issue B(but issue B is not a subtask is a issue i another project or sub-project) is automatically updated at the same way.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
+1 - This is definitely needed!
--------------------------------------------------------------------------------
+1 - Needed too as we are on a company which differenciate products and projects.
* Example :
One project manager declare a bug in his project but this bug is related to one product (which is an other "project" in redmine with SCM, wiki etc.)
We would like to create directly a ticket in the product part with more technical informations and when this ticket is closed it can unblock ticket created in project so as the project manager can see that his defect is resolved.
For now this only thing we can do is to go directly on the product, create a ticket and assign a link to the first ticket keeping his number in our memory and can lead to a mis-linking configuration.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1 same use-case as in comment 6
--------------------------------------------------------------------------------
related_issues
relates,New,17947,Mirror relation
duplicates,Closed,11613,Mirror issues