Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Custom field. Select bitbucket branches from drop down list when create issue



Is there a way or script to list bitbucket branch into a dropdown list that related to a Project Key.

The plan is that when create Jira Issue bug, we can select a branch from the list and it will appear in detail section. 

Product used is JIRA Server & Bitbucket Server.

Thanks in advance.

2 answers

+1 Looking for a free way to have a custom field that allows the user to select any existing branch on the Jira issue.

@Farhan Taib 
Let us know if you have solution for this. We are looking for a similar functionality.

Hello @Prashant Bagewadi 

You can accomplish this with the app Elements Connect (previously called nFeed).
(Disclaimer: I am the product manager of Elements Connect, I work for Elements)

Here is how:

  • Create an Application link between Jira and Bitbucket (preferred) OR create an Elements Connect datasource of type URL that point to Bitbucket REST API - Read the doc
  • Create an Elements Connect field of type "Live text" or "Snapshot text" (see the difference)
  • Configure the field, select the "Bitbucket" datasource
  • Field configuration is:
    • Query:
      where  PROJECT-KEY is the bitbucket project key and REPO-NAME is the bitbucket repository nam
    • Root element:
    • 1 json column:
      • Name: displayId - JSON Path: $.displayId
    • Key: 0 (if you selected "Live text")
    • Editor: Autocomplete (can be any type expect "Read only")
    • Template:

This is the configuration of a bitbucket repository picker. The text typed by the user in the autocomplete field is used to filter the query. ($userInput variable).

You can adapt this configuration to your needs and explore the Bitbucket configuration here:

If you have another question about Elements Connect, please contact our support team.

Hope it helps


Lead Product Manager @ Elements

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events