Real business use cases... pre-scripted!
This repository contains Simple Issue Language (SIL) sample scripts for use within The Power Portfolio suite of Atlassian Marketplace apps. These apps include:
- Power Scripts for JIRA
- Power Actions for JIRA
- Power Custom Fields
- Power Custom Fields PRO
- Power Database Fields
The Power Portfolio is currently only available on Jira Server or Data Center deployments. Simple Issue Language was written exclusively for Jira and your SIL scripts will always be forward, backward, and cross-compatible across Jira versions.
- katl-commons is required to enable the SIL Manager on any Jira Server or Data Center installation. It can be installed separately (for free), but is included and installed with download of any app within The Power Portfolio
- To actually execute SIL scripts, you must have at least one of The Power Portfolio apps installed. This repository is currently tailored with Power Scripts for JIRA in mind.
This example demonstrates how to download these script files onto your Jira server from the command line. It assumes a Linux deployment with Jira installed in default directories with default user:group as defined in Atlassian's documentation.
>> git clone https://bitbucket.cprime.io/scm/cap/sil-script-library.git
>> sudo cp -a sil-script-library/. /var/atlassian/application-data/jira/silprograms/
>> sudo chown -R jira:jira /var/atlassian/application-data/jira/silprograms
>> sudo find /var/atlassian/application-data/jira/silprograms -type d -exec chmod 755 {} \;
>> sudo find /var/atlassian/application-data/jira/silprograms -type f -exec chmod 644 {} \;Please note that this operation will overwrite any directories or files that you may already have on your application server if identical names are found. Continue reading for a more manual, selective approach.
The brute force method will work in a pinch if you want to be selective about which scripts to include in your instance and/or don't want to worry about the potential of overwriting any scripts you may already have in your instance.
The following sub-features must have scripts in the
root silprograms directory.
- Live Field listener scripts
- Live Field executor scripts
- silJQL scripts
Scripts invoked from any other triggering mechanism can be called from any arbitrary directory hierarchy.
Folders in the root directory of this repository are laid out by anticipated triggering mechanism. For example, we believe some scripts are better handled as "scheduler" scripts as opposed to "workflow post-function" scripts, but the boundary between them is not necessarily concrete. Scripts in the root directory (and subfolders of the root directory) should be operational for any arbitrary Jira deployment. There are a few exceptions:
- See Important Note above
- The !Examples-ModsRequired folder is laid out to mirror the root hierarchy. The differences is that scripts in these subfolders may not work in any arbitrary Jira deployment. The user is expected to reference these examples and either tweak variables as applicable or to use them as a learning tool for his or her unique needs.
- Simple Issue Language
- Power Scripts for JIRA
- Power Actions for JIRA
- Power Custom Fields
- Power Custom Fields PRO
- Power Database Fields
- Many of these examples were lifted from the Tutorials & Recipes documentation.
If you've solved a unique business request utilizing SIL in conjunction with any app from The Power Portfolio, we'd love to hear from you! We're willing to bet that many others in the Atlassian Community would love to hear from you as well. To showcase your script, please create a discussion topic and be sure to include:
- The request. What business need were you trying to solve?
- The app. Which Power Suite app(s) did you use to solve the need?
- The script. Please use the code editor in your discussion.
- The comments. Please comment your code so newbies can follow along!
- The tag. Please tag the discussion with
sil-script-library
If the business case seems common enough, we'd be honored to upload it to this repository so that others can benefit from your hard work. You will receive full attribution in the script comments, and we'll be happy to give you an upvote to bolster your community cred!
This project is unlicensed and is free for all to use and distribute in any manner that you wish. We ask only that you attribute the source material to cPrime, Inc., and specifically this repository, if any examples included here are reproduced in totality, without modification, in a public forum (blog post, marketing material, and the like).