Feature #11316

Automatic update of related issues

Added by Michał Chełmiński over 8 years ago. Updated over 1 year ago.

Status:ReopenedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:Invalid

Description

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.

Related issues

Related to Redmine - Patch #17947: Mirror relation New
Duplicated by Redmine - Feature #11613: Mirror issues Closed

History

#1 Updated by Etienne Massip over 8 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

This is already available via issues follows/recedes relationship type, please read RedmineIssues#Related-issues and issue subtasking (documentation at RedmineIssues#Subtasks is not accurate about this feature).

#2 Updated by Michał Chełmiński over 8 years ago

  • Status changed from Closed to Reopened

I know that this is possible in one project. I thought about the connections between issues in different projects?

#3 Updated by Michał Chełmiński over 8 years ago

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.

#4 Updated by Jean-Philippe Lang about 8 years ago

  • Subject changed from Automatic update of issues to Automatic update of related issues
  • Priority changed from High to Normal

#5 Updated by Jim McAleer about 8 years ago

+1 - This is definitely needed!

#6 Updated by Anthony BOUQUET about 8 years ago

+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.

#7 Updated by Toshi MARUYAMA about 6 years ago

#8 Updated by Inese Ez over 4 years ago

+1

#9 Updated by Thomas Feher over 1 year ago

+1 same use-case as in comment 6

Also available in: Atom PDF