how to create cross project linkages, perhaps at the component level

Question

I would like to be able to define cross-project linkages and dependencies.

At the 'task' level, this is fine (task to task).  However, I would like to be able to visualize in a workflow or dashboard all cross-project linkages and dependencies.  And, the other tasks may not be created yet.

Example:

Project A has a new issue, feature, enhancements, bug....it's in component C.  I need a validation and QA task in Project B, Project D, Project E to make sure that the issue reported (or fixed) in Project A does not effect the other projects.  Or, if it does, that this be addressed in Project B, E, and E as necessary.

Also, visualizing all projects in swim lanes with lines between components showing pre-defined cross linkages would be cool.

any thoughts on this process?  Is there a blog or forum where we can discuss this?

James Barwick · Answer

hehe.  perfect.  Yes, here is probably a good place.

I was trying to figure out how to do this with Confluence.  But confluence, although it has pointers and references, is still 'unstructured'.  Maybe that's good.  Don't know.

In any case, people need triggers.  They need workflow.  So, we have Jira service desk, which by the way is cool, but it's too limited.  It's designed for a single organization...example, I need SLA's for EACH organization, not the service desk staff...anyway...another conversation...

Because people need triggers, there needs to be something that happens when an issue is created.  Not just notifications for the staff responsible for specific components, but components that those components link to, etc. etc.

So, I can't see that confluence is going to work.

Any idea where there may be software that supports Cross-Project integration pooint notification and workflow?

Nic Brough -Adaptavist- · Answer

Ok, I misunderstood.

You're actually trying to represent project information rather than issue information.  Simply put, I don't think Jira is the place for this - the data you want to store and report on is not issue based, and although Jira groups things into "projects", it's not a Project tracker, it's an issue tracker.  Most places I've been use the project url to point to a linked Confluence space where they can document the cross project links, supporting documentation, progress reports and so-on.

(I'll try the link again - https://answers.atlassian.com- I really do mean you're already in the best place to discuss Atlassian products)

James Barwick · Answer

Hey Nic, your link to the 'best place' seems to have gotton dropped... can you post again?