Repository navigation
Import Jira Key as Windshift Key #416
Description
Hey,
i have imported a jira project recently, but unfortunately, I've realized, that the Windshift Keys were assigned completly random.
For example EXPL-30 will imported as EXPL-138 from jira.
Unfortunately, this means that mentions in commits no longer match, which prevents the productive use of the import feature.
Is this a conscious decision or is it possible to change this behavior?
Reacted by Stefan Ernst
Activity
[-]Jira import Jira Key as Windshift Key[/-][+]Import Jira Key as Windshift Key[/+]stefan-ernst commentedon Nov 1, 2026
hey, it was - sort of - deliberate. I wanted to preserve jira's rank field. Since Windshift uses a different ranking algo, translating lexorank to fractional indexes was too much work, so the simple design is: Just rank sort everything when reading from Jira and create items in the right order. Which leads to the key mismatch.
I think we can make this work however because we don't use a database sequence for the workitem keys - we can simply generate whatever workitem key we want. I will put this into the next version
feat(jira): preserve Jira issue numbers as item keys (WI-1957, #416)
stefan-ernst commentedon Nov 4, 2026
Hey @MDXDave closing this as resolved in 0.9.3, let me know if it works
MDXDave commentedon Nov 5, 2026
@stefan-ernst it works, thanks for the quick implementation!