You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there anyway to preset the component in the component field in issue collectors? or any other fields for that matter?
We create feedback forms for specific applications so we know what the component will be. However we have multiple components in the project that we do not want external clients to see in the drop down.
Hi
Thanks!!
This was very helpful! However it didnt completely answer the component part. It listed it for the basic fields like (Summary, description, name, etc...)
Component was a little bit different and after a bit of researching online with the information provided in the documentation, I was able to preset the component field with the following code
trigger function
...
fieldValues: { components: '10000' }
Hopefully they will update the documentation to provide this infomation in the future
Thanks again for the help!
Oh, sorry - didn't realize you wanted explicit instructions. Glad I was able to get you on the path to your answer though! :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does this mean that you have to use the Component ID or do you have a component named 10000?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The 10000 is the internal ID of the component value, not the ID of the field (as its not a custom field).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Components should not be set to their value but to their ID. This is a number as per the example above your post. you can find out the number by looking at the source code of the page that has the component field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, can you guys help me a little further with the components... i am not able to get the components field successfully prepopulated using the following. Everything else does populate. PSNOW is a valid component for the project. What am I missing?
fieldValues : {
summary : 'Test',
description : '123',
components : 'PSNOW',
fullname : 'Katy',
email : 'myemail@company.com'
},
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can! There are instructions for On Demand here. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.