How could issues get the "Closed" status?

Hi Sergio,

As you know, we aren't fully international compliant, and this is another instance, I'm sorry to say.

We actually trigger on the specific text "Closed".  So your status value has to include "Closed" in order for the process to stamp the Closed Date.

Same issue with a couple of other areas to be aware of:

In Security, there are settings to "Allow Approving of items" and "Allow closing of items". This controls the available status choices - if you cannot approve items, you won't see any status that includes the text "Approve" or "Reject". And if you cannot close items, you won't see any status that includes the text "Closed".

These are issues we need to look into as we work toward full unicode / international support.

Sorry for the inconvenience!

Hi.

In other tools there is a "switch" to be connected (by admin) with each "status", whatever language its value is written, and the switch could have three logical values:

• "Active" (as for open statuses)


• "Inactive" (as for frozen/suspended statuses)


• "Closed" (as for all closed/rejected/.. statuses)

Tool administrator chooses, for each status, either its name (local language), either the "logical value" for the switch above, letting the tool  correctly interpretate the logical status for any need.

This method could solve a situation, like mine, where there are at least four different "closed" conditions (Fixed with pach, really closed, suspended, rejected)



I think AlmComplete could have a great improvement in "status" handling: I think they are the "core" of defect/ticket/test management

Sergio