A three part answer...
First, don't do this, it's almost certainly a bad idea. Re-mapping status names is a recipe for disaster because you end up with two groups of people using different words for the same thing. Stick with one name for one item.
Second, in that vein, think about your requirement more carefully. You can easily extract a list of "In Progress" by using a filter that says "show me issue with a status of (in-progress or fixed)". Use that reporting instead. Your specific use-case actually suggests to me that you should set a "resolution" when going to Tested or Delivered, so that Jira reports on "open issues" (in progress as far as a customer is concerned, and in-progress or fixed to the developers) or "closed issues" for the other two. Might not be appropriate, but worth a thought. You could even write a spot of code - have a read-only field of "customer status", which you set in post-functions as issues move through the workflow. There are probably other things you can do which are also far better than renaming status by user group.
Third, if you absolutely must, then you could change the language. Briefly (I'll go into more detail if you really must), you define a new language for (say) developers, and then translate the status. You then need to tell developers to set their preferences to developer-english and make the customers use customer-english. They can be pretty much identical. It's a lot of work though, and still runs into the "using different language" problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.