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

Key: JRA-7624
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Mark Chaimungkalanont [Atlassian]
Votes: 33
Watchers: 21
Operations

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

Add time tracking fields to the RemoteIssue object

Created: 12/Aug/05 01:30 AM   Updated: 10/Jun/08 02:46 PM
Component/s: Remote API (SOAP & XML-RPC), Time Tracking
Affects Version/s: 3.3
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference
 

Participants: Anton Mazkovoi [Atlassian], Ben, Cameron Dunn, Edward Wagner, Ionut Scutaru, Jeremy Rishel, Mark Chaimungkalanont [Atlassian], Matt Doar, Nick Menere [Atlassian], Steve Brown and Wim Deblauwe
Since last comment: 5 weeks, 4 days ago
Support reference count: 4
Labels:


 Description  « Hide
Add time tracking fields to the RemoteIssue object

Fields like 'timetracking' should be added to RemoteIssue so that you can see them



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Steve Brown - 22/Jan/07 08:15 PM
please include "remainingEstimate" as well... currently can only see "originalEstimate"

Cameron Dunn - 04/Aug/07 08:45 AM
Is there any movement on this issue? This is a very important feature if you want to use jira for scheduled tasks (with an external scheduling system).

Anton Mazkovoi [Atlassian] - 05/Aug/07 05:24 PM
Cameron,

At the moment this feature is not scheduled, and therefore I am not able to provide a deadline for it.

Cheers,
Anton


Cameron Dunn - 05/Aug/07 06:51 PM

Thanks for getting back to me so quickly, Anton.

Getting this issue resolved is a serious part of our decision about whether to use jira or not. Can you at least tell me when it's going to be scheduled?

Cheers,
Cam


Anton Mazkovoi [Atlassian] - 05/Aug/07 11:10 PM - edited
Cameron,

Thanks for getting back to me so quickly, Anton.

Can you at least tell me when it's going to be scheduled?

Unfortunately at the moment I do not know. I know this is not very useful, however, I would hate to make a promise that we did not keep.

Cheers,
Anton


Matt Doar - 05/Sep/07 11:29 AM
Even though timetracking can be turned off, like voting, the fields should be present but not populated if not activated, I think.

Edward Wagner - 17/Oct/07 10:07 AM
Is there a way to create the issue and populate it when an assignee is designated later?

Nick Menere [Atlassian] - 18/Oct/07 12:10 AM
Edward,
As long as all compulsory fields are entered (i.e. assignee is not required), you create it and then update it later.

Cheers,
Nick


Ionut Scutaru - 14/Jan/08 06:13 AM
We are interested in this feature as well ! Please consider implementing it ..

Wim Deblauwe - 24/Jan/08 05:29 AM
Adding my vote to this issue. I started writing a SOAP client to get those values, but now I see this bug Is there anybody who has some kind of workaround?

Cameron Dunn - 24/Jan/08 06:42 AM
There is a workaround which I use.... but you're not going to like it

Fetch the page for the issue via http and parse the HTML.

Needless to say, this is incredibly painful and slow, especially when you have a lot of records.


Ben - 29/Apr/08 03:35 PM
Hi,
We are also interested in this feature. Best regards, ben

Jeremy Rishel - 10/Jun/08 02:46 PM
We're also very interested in this feature. Is there any known workaround using the remote API, rather than parsing the HTML?