Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 221965

Summary:

show timespent value in jira task editor attributes section

Product:

z_Archived

Reporter:

Eugene Kuleshov <ekuleshov>

Component:

Mylyn

Assignee:

Eugene Kuleshov <ekuleshov>

Status:

RESOLVED FIXED

QA Contact:

Severity:

enhancement

Priority:

Version:

unspecified

Target Milestone:

3.0

Hardware:

OS:

All

Whiteboard:

Attachments:

Description	Flags
fix	none
mylyn/context/zip	none
mylyn/context/zip	none

Description Eugene Kuleshov

2008-03-08 15:07:43 EST

One of the attributes of JIRA time management is "timespent" element included in the rss data for given issue:

<due></due>
<votes>0</votes>
<timeestimate seconds="0">0h</timeestimate>
<timespent seconds="46800">13h</timespent>            

It is already parsed into Issue.getActual(), but not mapped to the task data and is not shown in the editor

Comment 1 Eugene Kuleshov

2008-03-08 15:20:37 EST

Created attachment 91973 [details]
fix

added support for timespent attribute to jira task data handler and show read-only formatted value in the editor

Comment 2 Eugene Kuleshov

2008-03-08 15:20:39 EST

Created attachment 91974 [details]
mylyn/context/zip

Comment 3 Steffen Pingel

2008-04-02 00:52:35 EDT

Great patch! Thanks Eugene. I have extended the time formatter to also support weeks and days so the formatted values are consistent with the web interface. It is now also used to parse and format the values for estimates making it much more convenient to enter these values (bug 214039).

Comment 4 Steffen Pingel

2008-04-02 00:53:29 EDT

Marking as resolved.

Comment 5 Steffen Pingel

2008-04-02 00:53:31 EDT

Created attachment 94479 [details]
mylyn/context/zip

Comment 6 Eugene Kuleshov

2008-04-02 01:05:26 EDT

(In reply to comment #3)
> I have extended the time formatter to also support weeks and days so the 
> formatted values are consistent with the web interface. 

Steffen, please note that it is unsafe to format days and weeks because actual values depends on the server side settings, such as how many work hours is included in a day and how many days work week has. Without getting those settings from the server such formatting can result in a misleading results. Same problem is probably applies to the parsing.

Comment 7 Eugene Kuleshov

2008-04-02 01:14:02 EDT

See http://www.atlassian.com/software/jira/docs/v3.9/configure_timetracking.html

Corresponding configuration service:
http://docs.atlassian.com/software/jira/docs/api/rpc-jira-plugin/latest/com/atlassian/jira/rpc/soap/service/AdminServiceImpl.html#getConfiguration(com.opensymphony.user.User)
http://docs.atlassian.com/software/jira/docs/api/rpc-jira-plugin/latest/com/atlassian/jira/rpc/soap/beans/RemoteConfiguration.html

Comment 8 Steffen Pingel

2008-04-02 02:13:56 EDT

That's a good point. The JIRA connector might display inconsistent values with the web interface. I'll add a note to the FAQ.

Comment 9 Eugene Kuleshov

2008-04-02 11:15:25 EDT

 (In reply to comment #8)
> I'll add a note to the FAQ.

Why did you say it is not available? See comment #7 for the corresponding API. I've added bug 225358 to track this issue.

Comment 10 Steffen Pingel

2008-04-03 14:22:05 EDT

I have comment on bug 215109.