Smart commit with special characters in transition name

[Antoine Gauthier]

Hello,

I'm having trouble using some transitions with smart commits.

It appears that issue is limited to transitions having accented characters at the beginning or in the middle of their names.

For example:

• #recette-terminée => works OK
• #réalisation-terminée => fails KO

To better explain the issue I'm facing here is a screen shot of the transitions I'm using:

I tried renaming the transition and removing the accented characters from their names but that didn't help.

I also tried using the transition name without accented character but with the same results.

Any help would be greatly appreciated.

[Antoine Gauthier · Accepted solution]

Hello,

A bug had been reported but has also been closed without resolution :

https://jira.atlassian.com/browse/JSWCLOUD-20937 

The workaround suggestion is to :

Rename the workflow transition name to include non-accented characters in the first word.

I would actually go even further and suggest scraping any accented characters in the workflow transition name. 

To edit the workflow transition names without affecting the statuses, you should click on the arrow leading to the status and not on the status itself.

Regards,

Antoine

[John Funk]

Hi Antoine,

Can you share more information, such as the rule you have built? Or what error you are receiving? 

[Antoine Gauthier]

Hello John,

There is not much more to it, those are workflow transitions I'm trying to trigger using smart commits.

I'm not receiving any errors whatsoever.

We can see each message I tried to use on the issue all of them correctly displayed the accented characters: (once again the green ones worked and triggered the transition on the issue and the red one did not and this without any error)

[John Funk]

Do you have the status values in quotes? If so, you might try using the Status ID instead of the name. 

[Antoine Gauthier]

No I don't have statuses values in quotes, I only tried sending them in quotes to see if that would help by any chance but sadly that did not.

I Just tried sending the Status ID quoted and unquoted: no luck there.

[John Funk]

I would probably go ahead and open a Support Ticket with Atlassian:

https://support.atlassian.com/contact/#/

Please post the solution back here to help others who may search for this in the future and so we can close this post out. 

Good Luck!

[Antoine Gauthier]

I'm gonna try with a support ticket and keep this post updated.

Thank you John!

[Dain Henson]

Hi @Antoine Gauthier any luck with a support ticket? One of my devs is facing a similar problem in this case the transition name has a hyphen '-' in the name.

[Antoine Gauthier]

Hi,

The support ticket confirmed the bug, but sadly it hasn't been fixed yet:

 https://jira.atlassian.com/browse/JSWCLOUD-20937 

The good news is that I've been able to obtain a workaround from the support ticket :

While we were testing this, we found that the workaround to this issue is to rename the workflow transition name to include non-accented characters in the first word. Since the smart commits use workflow transition name and not the workflow status name, we would need to rename the transition name from "réalisation-terminée" to "realisation-terminée".

This seems to allow for the transition to be triggered, but I would actually go even further and suggest scraping any accented characters in the workflow transition name. The workaround would otherwise pick the first (of many transitions) if they contain accented characters after the first word.

As a side note, I haven't had any issues regarding transitions with hyphen(s) in the name, so perhaps double-checking the workflow transition names might be a good place to start.

To edit the workflow transition names without affecting the statuses, you should click on the arrow leading to the status and not on the status itself.

You would then be able to rename that workflow transition without impacting any of your views and filters.

Regards,

Antoine

[Dain Henson]

Many thanks @Antoine Gauthier , yes on closer inspection seems our issues are a bit different - my transitions have spaces and hyphen(s), and Jira actually uses hyphens to denote spaces in the smart commits - but you have definitely pointed me in the right direction. Will work with my dev for a solution.

Cheers!