Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Pivotal Tracker webhook owner nickname

yoshiotu September 16, 2019

We have Pivotal Tracker integration set up, and it is working ok except for new branches. In that case, the webhook request body JSON is missing a field that Pivotal Tracker requires.

Specifically, the "owner" object in the request JSON is missing the "nickname" field, and it includes the deprecated "username" field which is supposed to be gone as of April 19 2019 according to the bitbucket webhook docs.

Pivotal support suggested that there may be a setting in our bitbucket team profile or something that could be causing this. Does anyone know?

1 answer

1 accepted

0 votes
Answer accepted
seanaty
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 17, 2019

@yoshiotu It's a little confusing but repository owners can be either of type `team` or of type `user`.

User objects no longer have usernames and instead have nicknames (not unique)

Team objects still have usernames and don't have nicknames.

Because of this, it's best practice to really use UUIDs to identify repository owners since they both have this property.

Hopefully Pivotal can get their app updated. Do you mind linking to a page with information about the integration?

yoshiotu September 17, 2019

Thank you. That all makes sense. Here is the Pivotal Tracker documentation:

https://www.pivotaltracker.com/help/articles/bitbucket_integration/

yoshiotu September 19, 2019

With this information, Pivotal Tracker developers were able to implement a fix, and now it all works. Thanks again!

Like seanaty likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events