I'm trying to create a Custom Field type component, which grabs the project components.
if in JIRA I can create a custom field type version, why can't I create custom field type component?
Components are not a custom-field type, they are a system built-in field.
You ask why there is a version-picker but no component-picker - all it would do is duplicate the functionality the component field already does, and confuse the users (Which one do you actually fill in?)
Could you explain the use-case in case I'm missing something?
Let's say there's a UI component and a database component. 1) Someone implements a change to database component (e.g. changes the length of a string column) - change is delivered. 2) Defect is identified in the UI due to this change (e.g. because this column has changed size and the UI code was expecting the previous size). So if you're wanting to track and measure the source of defects to a system you may want to track the component where the cause was found separately to the component where a defect was fixed. There are other valid use-cases where you might want to have additional fields selecting from the Component list.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs