[Back in 2010 ...]
...
The problem with current functionalities is that we developed too many workflow actions (post functions) doing basically the same thing but linked to a certain field (for instance assignee, or reporter). The same observation is true for conditions and post functionsvalidators.
This is wrong, since the function is basically the same: we set a field value to a constant (including here the null value) , to another field's value or to a calculated value. The result is not flexible, certainly not configurable, and minimizes our chances when configuring a Jira installation.
...
Actually, we just needed something else: for us it made no sense to write import statements, or take care of the objects when all you needed to do is to set the assignee of an issue on a certain user. It was clear that we needed a new language. And because every language needs to bear a name, we called it SIL™ (Simple Issue Language™) and the containing app Power Scripts™ for Jira. Lack of inspiration, you may say.
...