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
Dear Community,
Asking for some ideas about best methodology to handle an unusual business case.
We have a department that has Jira issues that could possibly be linked to multiple vendor tickets and they'd like to track them on the Jira ticket.
Best I could come up with was a long text field since there's no way to know how many or few any one Jira ticket might have. Any other ideas?
I'd like to do a dropdown for the vendor at least but then how would I handle multiple vendors and external ticket id's.
Any suggestions are appreciated.
Best, Michael J
Hi @Michael Johnson , I am not sure I understand your requirements since what comes to mind as a solution would be to simply link each vendor issue to the singular Jira issue. Could you please provide more info on the requirements?
Hi @Jack Brickey ,
The external vendors have their own tracking systems, our team just wants to note them on the Jira ticket. But I suppose pasting in the link from the external system into a text field might work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you could add as comment. The question is how would you use this data? If you need to be able to search for it or Report metrics on it the answer might be different.
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.