Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Retrieving tempo customer key behind set tempo account

Hi everyone!

I have the following problem I need to solve in my company:

 

I have an issue with tempo account "A" set. This account is connected to the tempo customer "Z" with the tempo customer key* "123".

Now I want for the same issue to retrieve this tempo customer key "123" behind this account "A" and set this value ("123") as a custom field value at the same issue.

Is this possible?
Best would be if this is possible via nFeed, because I need this value afterwards to retrieve connected data via nFeed from a remote database. Maybe then I don't need the custom field anymore and use the customer key directly to retrieve the connected data from the remote database.


* https://tempo-io.atlassian.net/wiki/spaces/THC/pages/296812865/Creating+and+Deleting+Customers+-+Tempo+Server

 

It looks like this:

Screenshot - 04.07.2019 , 16_41_23_ver001.png

Thanks in advance for your time! :)
Roland Siegel

1 answer

1 accepted

1 vote
Answer accepted

Solved via Plugin "Elements Connect" (nFeed).

Live Text field using Jira REST API.
URL path: tempo-accounts/1/account/$issue.customfield_10400.id
(customfield_10400 is the Tempo Account field)

Columns
(Name | 
JSON path)
customerkey | customer.key

Thanks for the trick, It works fine.

Anyway the app is pretty expensive if used just for this purpose, so now I'll try to do the same via Scriptrunner.

Mr. Gonzales,
did you find a way to solve the problem with ScriptRunner? I am facing the same problem and would be interested in a ScriptRunner solution.

 

Thanks in advance.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events