Hi Tom,
As I understand the text of that issue, this is not something due for implementation in Jira as it is against the design philosophy. Unfortunately, none of the workarounds there are viable for Jira Agile as none would result in multiple avatars showing on a card. I understand that Atlassian may not use pair programming or consider issues in QA to be shared responsibilities between the Dev and QA assigned to it, but it makes it difficult when looking at a board to truly understand shared workload and WIP if only one face shows on a ticket actively shared between 2 or more people.
Is there any chance that Jira Agile will add either a feature or a method of extensibility to allow us to use a secondary user-type field as a trigger for an avatar? Is there any intention to allow configuration or plugins to modify the behavior of Jira Agile in this way? This would be tremendously empowering to our teams here and it is important to our roadmap to understand if this feature will ever be available or attainable for us through Jira and Jira Agile.
Suggestion
Hi Tom,
As I understand the text of that issue, this is not something due for implementation in Jira as it is against the design philosophy. Unfortunately, none of the workarounds there are viable for Jira Agile as none would result in multiple avatars showing on a card. I understand that Atlassian may not use pair programming or consider issues in QA to be shared responsibilities between the Dev and QA assigned to it, but it makes it difficult when looking at a board to truly understand shared workload and WIP if only one face shows on a ticket actively shared between 2 or more people.
Is there any chance that Jira Agile will add either a feature or a method of extensibility to allow us to use a secondary user-type field as a trigger for an avatar? Is there any intention to allow configuration or plugins to modify the behavior of Jira Agile in this way? This would be tremendously empowering to our teams here and it is important to our roadmap to understand if this feature will ever be available or attainable for us through Jira and Jira Agile.