Aliases is the most powerful thing in Jirio and allows create the most advanced flows and disrupt the way your team members communicate with each other.
Alias is a name of a custom built command that any Jirio user can compose and use later for its own specific needs. Think of it as a hot key for a command that you use very often and would like to avoid doing repetitive and tedious typing.
For example, you might be working in QA department and create 10 or 100 bugs a day. This involves a lot of typing of commands similar to this one:
/jirio create bug A user sees an error on login :components bugs :labels jirio :assignee tom.hanks
The only thing that changes in this command is a bug title. It would be much easier to type as less as possible boilerplate text and just enter a bug description only.
Aliases allow you to do it.
First define an alias with the “setalias” command. The command accepts an alias name (one word) followed by a command itself.
The syntax of the command is the following:
/jirio setalias [alias] [command]
/jirio setalias createbug create bug $1 :components bugs :labels jirio :assignee tom.hanks
This means that we created an alias “createbug” that has the following command “create bug $1 :components bugs :labels jirio :assignee tom.hanks”. You might also noticed that there is a “$1” that will be replaced with a first argument when running the “alias” command. You can also have $2, $3 and more parameters.
Now let’s use this command:
/jirio createbug "Another bug is here"
and when invoked, you will see that the actual command that will be executed is:
/jirio create bug Another bug is here :components bugs :labels jirio :assignee tom.hanks
Pretty cool, huh?
Notice, that when running the “alias” command, you will have to enclose each parameter into single or double quotes as otherwise Jirio will not be able to distinguish between multiple parameters.
Notice that you can also add channel default fields to the alias as well. The syntax is quite different, so make sure you check out this article.