nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

PostPlan with Rest API Tempo Planner

sjvisschers

I'm trying to post a plan via the Rest API Tempo Planner. I use the createPlan (postPlan) endpoint, but I continuously get a 'VALIDATION_FAILED' error.

I tested the authentication header I use with other API endpoints (such as getAllPlans) and there it works.

As request body I use the following. As assigneeKey I use the JIRA username, is this correct?

 {  "assigneeKey": "firstname.lastname",  "description": "Working hard on this issue",  "start": "2020-11-04",  "startTime": "09:00",  "end": "2020-11-04",  "day": "2020-11-04",  "planItemType": "ISSUE",  "planItemId": "4401",  "secondsPerDay": 3600,  "includeNonWorkingDays": false,  "partialUpdate": true}

What can I check to get this working?

Accepted answers

Alexander Eck [Tempo]

Hi,

as you already noticed the Tempo endpoint only accepts the userkey and not the username. You get the matching userkey from the username by calling the Jira REST API.

All comments

sjvisschers

It seems that Tempo Planner API uses a different key to identify the Jira User.
Jira and the Tempo Timesheet API use the field "key" to identify the User.

Tempo Planner API uses the field "Userkey" to identify the User.
In most cases this will be the same, but in some cases it seems to be a historical value.

I have filed a bugreport with Tempo. Hopefully the will changed it soon.

In the meanwhile, does anyone know how to get the "userkey" from JIRA?

Alexander Eck [Tempo]

Hi,

as you already noticed the Tempo endpoint only accepts the userkey and not the username. You get the matching userkey from the username by calling the Jira REST API.

sjvisschers

Thanks for your reply. It helped me a lot.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

rest-api

jira-server

tempo-planner