It will be great if you can help me for few requirement or direct me to one who can help here. I want to have some customization for one of my project. Below we want to achieve.
Need help building two custom fields:
1) New Custom Field1: Need help building a custom field that is a jql lookup where a user can choose among issues that are filtered via jql query and the resulting choice will show the issue key in a field. On save, the key value is clickable and will navigate the user to the chosen issue.
2) Where an issue is chosen, also add a 'features' link that will list the chosen issue among the linked issues (we have a custom linktype we've created called "features/is feature of")
3) New Custom Field2: Need help building a second custom field that calls the value of Field1. Wherever this field is shown, it will look for a Field1 value first on the Epic, then on the Story/Task. Where none is found on either, the field value should be set to the key of the current issue. This way the field will never be empty. (we will use configuration to enable these fields among different issuetypes on specific projects)
Please feel free to reach out to me or Michael if you have any question.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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