Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

there are several explanations about components, can someone help me understand if i can use components in the below scenario or do we have any field to use in my requirement. 

My team develop informatica code, its getting difficult to understand who is working on which code and are they stepping on each other. 

I am planning to add all the informatica job names to components so that i can assign them to the stories. This way when i try to migrate code to prod, i will be able to know all the stories that will move to prod 

Any suggestions ? 

1 answer

1 accepted

2 votes
Answer accepted
Fadoua Community Leader Feb 24, 2021


You mean:

Informatica Job 1

Informatica Job 2

The jobs will have different names if yes then yes you can add them as components to categorize the issues, you can even assign the component directly to the component lead



@Fadoua yes correct , create as Job1 , Job2 etc. 

Thanks for your response. 

Like Fadoua likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events