History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-6748
Type: Sub-task Sub-task
Status: Open Open
Priority: Major Major
Assignee: Sam Chang [Atlassian]
Reporter: Scott Farquhar [Atlassian]
Votes: 51
Watchers: 26
Operations

If you were logged in you would be able to see more operations.
JIRA
JRA-6747

Create 'link issue' system field

Created: 19/May/05 11:56 PM   Updated: 26/May/08 06:10 AM
Component/s: Issue Fields, Issue Links
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Part
 
Reference
 

Participants: Anne Diget, Anton Mazkovoi [Atlassian], Denis Yurkin, Derek Artz, Joanna Thurmann, Mark Chaisson, Mel Belacel, Nick Menere [Atlassian], Roman K, Sam Chang [Atlassian] and Scott Farquhar [Atlassian]
Since last comment: 26 weeks, 6 days ago
Support reference count: 3
Labels:


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] - 20/May/05 12:42 AM
The Link Issue system field should also be able to be a NavigableField, i.e. act as an Issue Navigator column, to show issue's links.

Anne Diget - 24/Oct/05 07:35 AM
Hi,

use of Jira will be "lighter" when it will be possible to link 2 issues at a workflow's transition (on a custom screen)...

Thank's for this improvement.


Anne Diget - 24/Oct/05 07:44 AM
... with the possibility to select the other issue among a list in a new screen (like in "link view")...

Roman K - 15/Dec/05 01:57 AM
Sometimes developers resolve an issue by specifying that it's a duplicate without finding the issue that it duplicates.
This feature will give a mandatory field so that the developers will have to find the duplicated issue.

Anne Diget - 29/Mar/06 10:31 AM
Hi,

I would like to know, if possible, if they're a deadline for the 3.6 version?
If you can say, thank's a lot,

Cheers,

Anne


Nick Menere [Atlassian] - 29/Mar/06 09:37 PM
Anne,

We decided to split the 3.6 release into 2 releases - 3.6 & 3.7, with 3.6 release coming forward. This is planned for 2 weeks.
The 3.7 release will come out when the 3.6 was originally planned. Unfortunately the only thing I know at the moment is, it wont make it into 3.6.

Sorry, I can't provide more information.

Cheers,
Nick


Denis Yurkin - 11/Jan/07 05:21 AM
Does it have a chance to become a part of 3.8?

Mel Belacel - 26/Jul/07 08:46 AM
Is this planned for next release?

Anton Mazkovoi [Atlassian] - 26/Jul/07 10:23 PM
Mel,

This is not currently planned.


Derek Artz - 31/Oct/07 08:30 PM
My company is looking at JIRA to support corporate certification for AS 9100, an Air Force process quality standard that is stricter than ISO 9001.

The certification requires that non-conforming products (the individual hardware failures) are tracked separately from the corrective action (approved solution for the failure). I would like to use the link view in a transition screen for a custom workflow I'm creating. This would identify the associated solutions for the hardware failures.

Thanks,
Derek


Joanna Thurmann - 01/Nov/07 07:22 PM
I added a vote from Polycom. We use clone and move functionality heavily in our database of nearly 100,000 JIRA issues. Having "link issue" system field available on screens and as a navigator column is key to finding (and reporting on) clones. We use other issue links, too, duplicates, depends on, blocks, etc.

Mark Chaisson - 17/Jan/08 08:11 AM
I would also like to use an "Issue Picker" field on one of my screens. It would be nice if it functioned just like the Issue Picker popup when the Link operation is selected. My Feature Request issue type screen needs this field, when a Feature Request issue is created, I want to link it to multiple Software Enhancement Requests.