Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321705 - Respect Jira fixVersion release date as Mylyn task due date
Summary: Respect Jira fixVersion release date as Mylyn task due date
Status: RESOLVED DUPLICATE of bug 270271
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-04 08:13 EDT by Chris Beams CLA
Modified: 2010-08-04 14:46 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Beams CLA 2010-08-04 08:13:54 EDT 
Submitting this against the Jira component, though I'm sure the functionality could be useful across most Mylyn connectors.

Scenario:

* I have several issues assigned to me for the upcoming 2.0 release of project XYZ
* Today is August 4th, and XYZ 2.0 has a release date in Jira of August 13th

Desired behavior:

* In the Mylyn Task List 'Scheduled' view, I should see these issues show up under the 'August 13th' date.
* As August 13th approaches and passes, I should see the task move up through the dates, and eventually turn red indicating it is due today / past due.

The functionality above is consistent with the way that local task due dates work today.

Of course, this linking of release date and due date could be made optional for users who do not desire it.
Comment 1 Steffen Pingel CLA 2010-08-04 14:46:25 EDT 
The Mylyn JIRA Connector has moved to Atlassian. Please file this bug and all future reports at: https://studio.atlassian.com/browse/PLE .

Please see this FAQ entry for further details: http://wiki.eclipse.org/Mylyn/FAQ#What_happened_to_the_Mylyn_JIRA_Connector.3F .

*** This bug has been marked as a duplicate of bug 270271 ***