Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to get the versions List of a JIRA Project From Confluence??

In confluence, I want to get a list of versions of a specific JIRA project.

What are the possible API that could be used in this sitaution?

 

Regards

 

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted

Here are 2 solutions:

  1. JIRA Version List Using the JSON Table Macro - this is available with Advanced Tables for Confluence
  2. You can use the CLI Macro (from Run CLI Actions in Confluence) with the following action:
--action getVersionList --project JCLI --outputFormat 2

Hi Bob,

I installed JCLI on Confluence (application linked to our JIRA server instance) and placed the CLI Macro on a Confluence page.  I pasted the action string shown above (project key in JIRA is CRM)

--action getVersionList --project CRM --outputFormat 2

It responds with REMOTE_EXCEPTION

Remote error: User is not authorized to perform the request. Response code: 401.

 That would suggest that I need to authenticate, but I could not find how in your online docs.

Thank you 

You need to provide user and password parameters for practically any CLI action no matter where it is run. So, for instance, you can provide them directly on the action request. Normally when using a command line directly, you hide them away in a initial script file (atlassian, confluence, jira, ... templates provided) so you never need to type them again :). Similarly, when using CLI macro or similar embedded support, you hide them away in a profile so you don't need to repeat them for each use. This also protects them from being seen by others as part of the page source. If you have untrusted users on your site, you will need to protect the usage of the profile using Macro Security. For more information on profiles, see Profiles.

Like mchrobok likes this

Thanks, Bob - that gives me good direction.  And thanks for the fast response!

TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

267 views 16 17
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you