ASCII characters - impossible to save my workflow

[Caroline_Muon]

I want change a workflow who is in company managed but I have always the same message : impossible to save, you use ASCII characters

As a french, we have specials characters in the status & transitions for exemple : bloquée, à faire...

The last change was in april without this message.

There is a change recently ? Do I need to change my workflow by deleting accents & other characters ?

Thanks for your help

[Caroline_Muon · Accepted solution]

Thanks all for your answers

I will open a ticket

[Andy Heinzer · Accepted solution]

Hi @Caroline_Muon 

I understand that you are trying to save a workflow name in Jira Cloud, but you are unable to.  The error message indicates that you must use ASCII characters. 

It's true, the workflow names are required to use ASCII characters only.  I am afraid that accented characters fall outside the scope of what ASCII can represent.  As such characters like é or à or í cannot be represented in ASCII itself.

We have a feature request for this over in https://jira.atlassian.com/browse/JRACLOUD-41875

In the meantime, you will need to adjust the name to use non-accented characters in the name of the workflow.

Andy

[Matt Doar _Adaptavist_]

Andy, the original post is about accents in status names and transition names. I thought that UTF8 was supported in those places, but I guess not? I couldn't find jac work items about those specificaly, can you?

[Andy Heinzer]

My understanding is that this is not about the status names or transitions.  Statuses and transitions can use UTF8 or translations with allow UTF8 characters.  In this case though, the problem is in the name of the workflow itself.  That workflow name can't use all UTF8 characters.  It has to use ASCII characters only.

[Matt Doar _Adaptavist_]

Tu te trompes, mon ami.

From the OP:

"As a french, we have specials characters in the status & transitions for exemple : bloquée, à faire..."

[Andy Heinzer]

My French is not good :)  And I admit I'm often wrong about many things.

I realize what is being reported here.  However in my testing of this on Jira Cloud today, I was able to create transitions and statuses with accented characters.  Hence that part isn't the limitation being seen by the OP.

In my testing, the name of the workflow itself is where I see this warning, like so:

So doing a copy of a workflow, editing the workflow name, these are places where you might see a message like this.  I believe this is the warning/error the OP is referring to.  But the cause is not in the statuses or transition names.  The cause in this case is specifically in the name of the workflow itself.  How this happened for this customer, I cannot yet say. Perhaps there was a bug or an unexpected means of migrating workflow data from a data center environment of Jira.  These things shouldn't have happened, but without a closer examination by support of that environment, it's difficult to say what might have caused this.

My research on the topic seems to indicate that this specific workflow name limitation is very old in terms of the life of Jira.

That said, if I'm wrong or have misunderstood the problem reported, please accept my apologies, I'm here to learn as well.

[Matt Doar _Adaptavist_]

No apology needed, nice work digging into this one!

[Shawn Doyle - ReleaseTEAM · Accepted solution]

Hi @Caroline_Muon 

You shouldn't need to change the names or values of your fields; this seems like a bug Atlassian introduced, and you should put in a support ticket.  I will mark this question for support to look at.