nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

External IDs Missing From Features

Thomas Dennis_8w6sn3

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

Accepted answers

Rich Sparks

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.

All comments

Rich Sparks

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

Tim Keyes

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!

Thomas Dennis_8w6sn3

@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!!

Tim Keyes

Great to hear.

Thank you for the update.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-align