-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JIRA: create worklog entry after stopping the timer #28
Comments
JIRA has REST API that supports authentication via cookies (so you don't have to obtain any additional tokens when issuing a request from within a browser), however it requires quite a lot of data to be supplied: {
"self": "http://www.example.com/jira/rest/api/2/issue/10010/worklog/10000",
"author": {
"self": "http://www.example.com/jira/rest/api/2/user?username=fred",
"name": "fred",
"displayName": "Fred F. User",
"active": false
},
"updateAuthor": {
"self": "http://www.example.com/jira/rest/api/2/user?username=fred",
"name": "fred",
"displayName": "Fred F. User",
"active": false
},
"comment": "I did some work here.",
"visibility": {
"type": "group",
"value": "jira-developers"
},
"started": "2014-01-06T00:00:12.707+0000",
"timeSpent": "3h 20m",
"timeSpentSeconds": 12000,
"id": "100028"
} Tried omitting some parameters and the server didn't like it, will investigate further... |
My bad, I just forgot the {
"comment": "I did some work here.",
"started": "2014-01-06T00:00:12.707+0000",
"timeSpentSeconds": 12000
} Even the Looks doable. |
@dpashkevich - looking into this issue now I'd say we do not intend to post data to JIRA as well in addition to Toggl. But we do have "pipes" (https://github.com/toggl/pipes-api and https://github.com/toggl/pipes-ui) that is fully open-source and can be used to export entries to JIRA. Might want to take a look into it... |
This is actually the main problem I expect from toggl-button to solve, because at the moment we manually copy Toggl time entries to Jira worklog which is inconvenient and error-prone...
The text was updated successfully, but these errors were encountered: