Garden Gloves-96

I spent a part of the summer with my parents in a beautiful place in France where my parents are now retired, enjoying family moments and talking about darwyn launch and what we did with our customers.

My father was really curious about JIRA Software and I spent time with him showing him what can be done thanks to JIRA Software. I introduced to him my FISH inventory system (see the darwyn blogpost here and Atlassian article over there) and he was really impressed about the simplicity of the system and all indicators that I am able to get now.

a GARDEN inventory system running on JIRA Software


While we were working in the garden, my father made a simple reflexion: “It’s too dry, this summer is really hot and I always forgot about watering the garden…”. Out of nowhere, the sentence popped in my mind: I should implement a system that will notify him about watering the garden, using JIRA Software of course!

I should keep it simple for him to let him know when it’s time to watering the garden. That’s all he needs to know… Eventually he will be able to follow the growth of plants and that’s it! The idea of a GARDEN inventory system on JIRA Software was born!

I will show you now how I implemented the system: we will dig into the advanced workflow configuration of the project and how did I setup automation on this project.

Setting it up

I created a project and simply named it GARDEN, using JIRA Software default KANBAN configuration. Why KANBAN? A garden is a flow of plants, it never really stops except during winter, each plant have a specific states, everybody knows that KANBAN is perfect for that.

For this project, I added also:

  • one specific issuetype: seed
  • a dedicated workflow for this project: Garden – Vx.x (Vx.x is used for versioning the workflow)
  • an automation rule for all issues: using Automation for JIRA add-on (cloud)


Every plant has a cycle, nature does things well: from growth to bloom, from bloom to harvest, and after the harvest you remove the plant out of the ground (most of the time). Then, every 3 days, you need to water the plant. Simple isn’t it ?!?


Advanced workflow configuration: conditions

My father is not really used to JIRA Software, so I should make his life easier and restrict all transitions between status. Using the KANBAN board, he will be able to move issues (here we talk about seeds) between status without asking himself which status to use. This is why I added conditions to let him move the seed easily to the correct status.

Back to grow conditions


The idea here is to condition the transition to allow it depending on the previous status, when the plant grows and needs water, after watering it, he should move it back to grow and the bloom status should be not allowed.

Back to bloom condition


Same here: when the plant is blooming, he can’t put it back to grow after watering it.

Need water: global transition conditions


I used a global transition to make it simple in the configuration and reused the transition called “Need water”. Conditions  are here to block the transition: during harvest, we don’t need to water the plant, and when the plant is done, water is not needed as well.

To be able to use the Previous Status condition in the workflow advanced configuration, I used another great add-on which I consider as a must-have in all Atlassian JIRA Core / Software platforms: JIRA Misc Workflow Extensions add-on (cloud or server).

Automation rule

Automation for JIRA add-on (cloud)


Setting up a rule using the add-on is really easy: thanks to a JQL filter, a list of issues will be selected and in that case, I need to transition the issue (seed) to the status “NEED WATER” to allow my father to easily know which plant needs water. I could have done it in another complex way but for now, all I need is to automate the transition.

How it works for this case: based on the JQL filter for this project, excluding Harvest and Resolved issues, we are looking for non-updated issues since 3 days. With this list of issues, the transition NEED WATER will be triggered on each of them. The rule is executed every day to check if there is a plant that need water every day. That’s it! The automation is done for this project.

KANBAN board

Using the dedicated project KANBAN board, which I organized according to the workflow of this project, my dad is now able to drag and drop each seed (issue) in the appropriate status. This is really simple and now my father is able to follow up his garden inventory.

Transition using drag and drop on the Kanban board


Mobile features

To be able to follow easily all seeds, I installed the JIRA mobile application on my dad’s phone. Well, I am “cheating” a bit because here you can see a screenshot of the application’s beta to be able to use all great new features of the app. Atlassian mobile team is working hard on it and it’s a pleasure to send all my feedbacks.

Mobile notifications


Mobile Kanban board screenshot (application’s beta)


Step back a minute

Furthermore, a gadgets board was build also to have few statistics about the garden. What does my father need to know: How many plants needs water? how many plant is in grow and bloom status? What kind of vegetable are in the ground? Optimizing the garden to make a better homemade production can be good for the planet and for our stomach ;-).

by status


by type of vegetable (using components)


Going forward

Was it hard to setup this project? NO, not really, the tricky part was on all workflow conditions, but you get used to it quickly. I’m really following up  the mobile application because all my projects (especially the FISH one) need to be improved, especially to create issue using custom fields. I want to do more with the automation add-on on other projects especially for automatic attribution and automatic comments.

I hope you like this article, don’t hesitate to send us feedbacks and comments in here or directly on our Support Center using our JIRA Service Desk in the cloud.