New Issue Type for Components Meta Data

[Severin Wirth]

Hi there

We have a request where we want to add a new Issue Type for Compontents Meta Data. We already have an Issue Type for Project Meta Data and need now something like a "Child Object" where we can store the meta data for all the components which are assigned to the specific project. 

The link between the Project and the Project Meta Data issue is done by the selection of the Jira project within the Project Meta Data issue. We need something similar now on the Component Meta Data Issue.

We tried with the components picker but have the problem now that we only can pick components which were assigned to our Project Meta Data issue and not to the jira project.

Thank you very much

[Nic Brough -Adaptavist- · Accepted solution]

You can't do this - as you've discovered, components are project items, and your metadata issues are in a different project to the ones you're trying to document.

There are a few options:

Drop components from the metadata project and use a custom field for them

Add all the components from the other projects as components in the metadata project (bearing in mind they will be different components, just with the same name)

Find or write an app that can represent your components in your meta data project.  (I did this with a scripted field, so I didn't need to do any maintenance work - the field looked at the linked project, read the component list, and displayed them all on the issue)

[Severin Wirth]

Hello Nic

thanks a lot for your feedback. Glad someone understood what I was trying to ask :)

Any chance you could provide us with a "preview" or example of your script solution? That would help us a lot, as we are still quite new to this topic overall.

Many thanks!