Harvest Time Tracking plugin for JIRA Cloud - by Strategery

Building the project

1. Copy the .env.prod or .env.dev file into .env and modify to your needs.
   • Make sure you set the correct value for the NODE_ENV variable: production mode will enable obfuscation and domain lock; development mode will generate source maps.
   • BASE_DOMAIN variable should contain the domain name under which the app will be publicly accessible.
   • BASE_PATH variable should contain the path portion of the base URL under which the app will be publicly accessible.
   • HARVEST_CLIENT_ID should contain OAuth2 application client ID that you can obtain in the Harvest settings section. Please note that the application redirect URI should point to exactly the same domain you specified in the BASE_DOMAIN variable. Wildcard domains won't work for client-side applications.
2. Run npm install to install all required dependencies
3. Run npm run build to build the project.

You can find compiled files in the dist folder.

Running the app locally

To successfully add the app to JIRA it should be publicly accessible with HTTPS protocol. Usually it's hard to achieve on a developer machine. In that case it's easier to use ngrok.io:

1. Start ngrok and point it to your local web server: for example, ngrok http 80 or ngrok http -host-header=rewrite strategery-jira-harvest.test:80.
2. Set the BASE_DOMAIN variable in your .env file to the domain name of your ngrok tunnel instance (e.g. 71e6574d.ngrok.io).
3. Build the app.
4. Update the Redirect URI of the OAuth app in Harvest.
5. Add the add-on to your JIRA through the 'Upload add-on' option using the URL to your atlassian-connect.json file (e.g. https://71e6574d.ngrok.io/atlassian-connect.json).

Also, npm run watch is useful when developing to do incremental compilation for changed files only.