You'll need to write some code for that.
I'm not sure you'd want to do it as a checkbox too - JIRA Agile users often generate a large number of boards quite quickly, and it's not unknown to find a JIRA with hundreds of them, which doesn't really translate cleanly into a neat checkbox.
I think it might be easier for you to explain the reason behind asking for a field like this - what are you trying to achieve?
Hi @Nic Brough [Adaptavist],
if a JIRA ticket is created on Team A's project and some of the work requires Team B to complete the work, one of the following things happens:
In both cases, often the result is Team A never knows the status of the ticket unless they look it up on Team B's JIRA Agile board. This results in a lack of visibility on similar issues.
Proposed New Process: "Interdisciplinary"
I think that covers it. Thoughts?
I can't see how a custom field with a list of boards would be any better than a simple flag field on the issue saying "interdisciplinary". It's actually worse, because the list of boards is going to change and adding a new board is going to require you to go back over the field and get the humans to update it (not to mention the coding, and the ugliness of having hundreds of options on screen). Boards are very much designed to work on the data on issues, so a simple "interdiscplinary" flag will be easily filterable to generate your board. All the other proposals above also require action on the part of the users, and simply setting a flag is probably an easier interface than the others.
Hi @Nic Brough [Adaptavist] , The problem with a single, unified interdisciplinary flag would be that ALL boards would see tickets where the flag is checked. We want teams to explicitly subscribe themselves (or be subscribed by another team) to specific tickets where they have a vested interest -- and remain subscribed until that subscription is removed. The interdisciplinary feature should permit 0 to n team subscriptions. I just don't want to have to update the interdisciplinary field every time a new team board is created. I'd rather it auto-populate the field's selection choices by querying the database for a list of boards. But you do bring up a point -- would refreshing the list of board choices blow away existing subscriptions? Hmmmm....
Hmm, that really does make a lot of sense, I hadn't really grasped that before. An idea on improving the idea of a simple flag - instead of a really plain checkbox, use a custom field of some sort. There's a few options here - a multi-select naming the "interested teams" would be a much better option than a simple "interdisciplinary" flag because you could write filters (and hence boards) like "interested team = x". The difficulty here is that you have no way to generate "a list of boards" - anyone can create boards and there's no real way to make that useful. If you stick to a "team is interested" flag on issues, then the board issue goes away.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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