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

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
4,559,606
Community Members
 
Community Events
185
Community Groups

External IDs Missing From Features

Yesterday we noticed, when creating new features, the External IDs are not populating. I've checked the new Features against existing with External IDs and the setup is identical. Has anybody else seen this or know what this could be causing this?

Thank, Tom

image.png

1 answer

1 accepted

1 vote
Answer accepted
Rich Sparks
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 06, 2021 • edited

It looks like some features are getting written to Jira and others are not. In the sample you have open, it is to be written to the "BR DCK" project, and it hasn't been written there yet. (You can tell this because there's no external ID in the feature grid, and also because there's no "View in Jira" button on the Details panel.)

Is it the case that the other items that weren't written to Jira go to the same Jira project?

You could have your Jira Align system administrator check the Jira connector logs (Administration > Jira Settings > View Logs) and check if there are errors related to writing to that project. Sometimes Jira projects have different permission schemes or attributes, and the connector account doesn't have the appropriate access to that account.

Tim Keyes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 06, 2021

Hi Thomas,  I checked our backend logs for this sync and found the owner of the Feature is unable to be assigned issues on the BRDCX Project.  Adding the Owner of the Jira Align Feature as an Assignable user on that project and updating the Feature again in Jira Align should make the Feature sync.

This error should also be Captured in the Jira Settings > View Logs as Rich stated.


Thank you!

Like Brian Weissman likes this

@Tim Keyes @Rich Sparks : Thanks but figured this out on my own. :) This was caused by two different issues and by going into the Audit Log and finding the problem for each. The first was as you stated, the individual creating the Feature, had not been added to the project in Jira Cloud. I went in and added the user to the project in JC, had them go back into the Feature in Jira Align and had them create a user story and voila! The sync started and the EXT ID was generated.

For the second, the Audit Log revealed the Features "Summary" field length had gone over 255 characters causing the sync issue. Once they took it under 255, sync occurred and EXT ID generated.

The journey to being a good Jira Align Admin continues! :)

Thanks again to you both!!

Like # people like this
Tim Keyes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 06, 2021

Great to hear. 

Thank you for the update.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events