Ability to create a parent change record and associate multiple child changes to the parent.
How do you envision this?
Aside from a simple solution of being able to attache changes to changes.
That is basically it, attaching changes to changes. Also, a way to identify from a change record if it is a parent/singleton versus child and if child, it's associated parent and siblings.
I could see this being a great tool for managing the separate changes involved with a project or operations change. Good idea!
Also, if a sibling has a dependency on another sibling. For example, moving a web site change with database changes. The database changes would be needed in order for the web site changes to also be moved.
I would like to see this parent / child relationship too.
Currently, for example, you can associate multiple incidents to one Change, but it would be good if multiple Change could also be associated to a 'parent' Change as well.
Change 001 - 'Parent' Change Change 002 - Child of Change 001
Incident 001 - Used to create Change 002
Change 003 - Child of Change 001
Change 004 - Child of Change 001
Incident 002 - Used to create Change 004
Incident 003 - Associated with Change 004
Incident 004 - Associated with Change 004
In the example above, a number of separate incidents were created (indents 001 through 004) and associated Changes were made or added. The Changes are then child Changes of a larger project (in this case, Change 001).
Pretty much what you said Yuval Pecht - attaching Changes to Changes
This would help a lot on large development projects.
For what its worth - it would be nice to do that 'Contracts' too.
Retrieving data ...