Attributes on Links (Issue-Issue-links)

[Mark Bednarski]

Hi,

We evaluating Jira in some pilot projects but having a problem with simple use cases. I hope someone could tell us how this is setup in Jira, must be a basic question I know, but was not able to find any answer on the Atlassian pages and related blogs.

h2. Customer rating on tickets

What we want to do is having the ability that a customer can rate issues in a KANO analysis way.

What we wanted to do: Import all customers as tickets and create links from the stakeholder issue to the technical issue. But unfortunately I don't see a way to attach a property to this link where I can save the value.

h2. Customer ticket ID

Similar like above. We need to to link a customer (stakeholder issue ticket) with a technical ticket (bug or feature request) and store the ticket ID of the customer for this relation. Again we thought this can be done with attributes on links, but I don't see how to create them.

Without the ability to track the customer IDs I can't report the contractual status to our customers, this would be a showstopper. Same for product management if they are not able to give ratings for individual customers.

I would really appreciate if someone can educate me an tell me what I'm doing wrong. It must be so obvious...

Thanks

Mark

[Ed Schriger]

We would like a link attribute "enhances"/"is enhanced by".

Many times we will deliver on a story and a need will arise to enhance it. It was built correctly and the functionality is correct - it just needs some enhancement.

If the JIRA Issue Link Attributes list is fixed, how can these requests be promoted?

[Igor Sereda [ALM Works]]

Hi Mark,

There's no way to have additional attributes associated with standard JIRA links. The only attribute is the link type.

One solution would be -- in case you have few values for this link rating -- is to have one link type per attribute value, that is, instead of

"stakeholder" ----requires----> "technical ticket"

have

"stakeholder" ----requires (High Priority)----> "technical ticket"
"stakeholder" ----requires (Medium Priority)----> "technical ticket"
"stakeholder" ----requires (Low Priority)----> "technical ticket"

Another solution I can think of is to store the priority in a custom field - but it will not be clear which stakeholder is the source of the priority.

Hope this helps,
Igor