Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I add information to a Component definition

I want to add a Component Group and a file link to a component definition. Any ideas?

1 answer

Hi @Huw Lewis 

I do not believe you can do that with out-of-the-box Jira Cloud.  There may be a marketplace add-on for purchase that can support that.

As a work-around, you could try entity properties at a project level, with name/value pairs based upon the Component.  These can be accessed with the REST API, automation for Jira, and marketplace add-ons.

However, if we pause implementation for a moment, what problem are you trying to solve by associating those attributes to the components?

Best regards,


Hi Bill,

Thanks for the reply. At the moment I’m looking at a specific issue. I have graphic designers generating Icons, Avatars etc in Adobe Xs with their product being stored in the Xd Cloud. Since these graphic components are used in multiple screens I define them as components so I have a “used on” view. To compliment this I hoped to include a link to the stored location.

Later, I will have a similar task to do again with multilingual text components.

Got it, and thanks for explaining!

With current built-in features, have you considered asking your site admin to add custom fields for this: e.g. Screen Assets.  You could then:

  • set the field manually, as issues set their component (i.e. screen), or
  • use an automation for Jira (A4J) project rule to set the field when the component value changes, selecting the appropriate storage location/URL

For automation, you would need to maintain the rules as the components and URLs change, but it would save some effort.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you