...
...
...
...
...
...
...
...
...
...
...
...
[Back in 2010 ...]
It all started when a customer requested us to do the same validator in 3 different ways. Then, the company (a bank) thought that it would be nice to add a very complicated logic behind, logic that should be changed anyway on the real Jira production system. In the meantime, another customer came and asked us to do the same, but in a slightly different way.
...
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.
...
It's true, syntax was very crude, the editors were not very pleasant to use. But it worked so well.
[... in the meantime ...]
Armed with this tool we had some huge Jira customization projects. There are Jira instances out-there that one would need for sure to take a second look to convince herself / himself that it is a Jira for REAL !
And we just got better and better, simplifying the syntax, adding functionality over functionality, routine over routine, support for many more custom fields.
[... and the present]
We established ourselves as a provider for very complex Jira solutions. SIL™ has just made its way in 6 of our public apps:
- Power Scripts™ for Jira
- Power Actions™ for Jira
- Power Custom Fields™
- Power Custom Fields PRO™
- Power Database Fields PRO™
- SIL Excel Reporting
And still we're getting better.