Is it possible to have a worklow exclusive to a component within a project? (Jira CLoud)

[Jamie Draper]

I have a project with 6 major milestones (which i created components for) but I want to exclusively link certain workflows to only one or two of them.  Is this possible?

[Nic Brough -Adaptavist-]

No.  Workflows are applied to issue types within projects.  Not components.

[Jamie Draper]

Thanks Nic, propbaly a poor use of terminology in the inital question.  Can Issues be linked to select Components?

[Craig Castle-Mead]

Hey Jamie,

Components are project specific, and can't be more controlled than that, so I don't think your use case of specific issue types to components is possible.

CCM

[Nic Brough -Adaptavist-]

You can "link" issues to components - you select the components you want to link by entering them in the components field on the issue.  But I don't think that's what you mean.

[Jamie Draper]

Thanks both Nic and Craig for your input.  What I was trying to achieve was to utilise 'Components' as mini-projects to link departments rather than have six projects which captured each milestone phase. 

The overall relationship between the 'Components' in this instance is linear and I wanted to script the creation of the next issue for the subsequent 'Component'. Essentially generating a scripted workflow between components.  I explored alt means of having a 'Governance' styled master Issue instead of components but the limitations in the Sub-task depth (ie No sub-task of sub-tasks) made this difficult. 

Likewise generating scripted links and blocker / relates to relationships was getting messy.  Cloning of tasks across the enterprise partners (who all run their own JIRA [desktop] instances in addition to the common customer [cloud] instance) often led to a lag between where an issue was actually at. 

Each 'Component' held a parent Issue Type (ie. Start-up, Needs Analysis, Detailed Resourcing, Production, Acceptance and Close-out) that would be unique to that 'Component' 

I was really looking to find a way to prevent the user from creating a 'Needs Analysis' Issue when that series of tasks was actually in the 'Production' stage / component.