[#JRA-4444] XML/RSS for sub-issue doesn't identify parent issue.

JIRA

XML/RSS for sub-issue doesn't identify parent issue.

Created: 03/Sep/04 12:37 AM Updated: 30/Jul/06 07:37 PM

Component/s:

Web interface

Affects Version/s:

3.0 Pro Preview

Fix Version/s:

3.7

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

~~JRA-4443~~ RSS/XML Issue entries don't identify sub-issues

~~JRA-10404~~ Make 'views' of content (single issue and search request) pluggable, and rewrite default implementations in velocity

Participants:	Jeff Turner [Atlassian], Mark Derricutt and Scott Farquhar [Atlassian]
Since last comment:	2 years, 8 weeks, 1 day ago
Resolution Date:	04/Jul/06 08:27 AM
Labels:

Description

« Hide

When an issue is a sub-issue, the RSS/XML description of an item doesn't identify itself as being a sub-issue or which issue is its parent.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 03/Sep/04 01:07 AM

Sub-issues are implemented as a special link type. Would a block of XML like the following be sufficient?

Or what info do you need?

[ Permlink | « Hide ]

Mark Derricutt added a comment - 03/Sep/04 01:19 AM

That would work well, although another thought just hit me - the link list is just another RSS feed.

So you could just include a <linked-issues-feed>.../someurl</linked-issues-feed> ( or suitable element name ).

[ Permlink | « Hide ]

Mark Derricutt added a comment - 03/Sep/04 01:20 AM

Just thinking about that, the generated RSS for the links should include a tag that says what the link type is. So is slightly different to the standard RSS feed...

Thoughts?

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 03/Sep/04 01:31 AM

In HTML it could be <a href="..." rel="subtask"/>. Whether a full URL or issue key is returned depends on what people want to use it for.

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 04/Jul/06 08:25 AM

This is implemented in JIRA 3.7. The XML looks like this:

<parent id="$issue.parent.id">$issue.parent.key</parent>

Cheers,
Scott