Automations are accessible to all Fibery plans without limitations.

Check out our webinar for detailed explanations and join our community to dive deeper into real cases!

Let's check, how can Fibery Automation Rules improve and automate your Software Development process.

Cases:

  • Create new sprints automatically 🏃‍♀️

  • Automatically mark Sprints as Done ✔

  • Change Bug priority based on the number of complaints 🐛

  • Change Story priority when Due Date is coming ⌚

  • Assign QA when Bug is ready for testing 🦐

  • When the feature is ready set all stories and bugs as Done 🚀

Sprint Planning

Create new sprints automatically 🏃‍♀️

Expected result: new Sprint will be created in 1 week after the previous ended with two weeks duration

Rule:

Formula:

Noted!

  • you have to add a 1:1 relations between Sprint and Sprint Type. So each Sprint would have a Previous Sprint and Next Sprint

  • Here is a pro guide of how to set Duration formulas in Fibery

Automatically mark Sprints as Done ✔

Expected result: Sprint will be moved to Done State when its End date is Today.

Rule:

Prioritizing

Change Bug priority based on the number of complaints 🐛

Expected result: when more than 2 users reported the bug - change Priority to Urgent

Rule:

Noted!

  • you have to add a # of complaints Formula to the But Type.

References.Count()
  • you also need to have a Priority Field. Let it be a Single Select

  • collecting Bug reports is a part of a feedback process - check our blog post about it

Change Story priority when Due Date is coming ⌚

Expected result: when Due Date for the Story is coming - Notify Assignee and change Priority to Urgent

Rule:

Noted!

  • you have to add the Due Date field (single Date without Duration)

  • you also need to have a Priority Field. Let it be a Single Select

Workflow Improvements

Assign QA when Bug is ready for testing 🦐

Expected result: When Bug or Story moves to the "To Test" State - assign QA

Rule:

If you have many QA ✨ - you can make an alternative rule - Notify all QA in your company and let them decide, who will take the bug

If you have too many QA and what to notify the one, who has fewer bugs&stories assigned - contact us via Intercom and we would be glad to set it up together 🤗

When the feature is ready set all stories and bugs as Done ⌛

Expected result: when the feature is ready set all stories and bugs as Done (sorry, just failed to find other words not similar to the name)

Rule:

If you have other cases in mind, feel free to contact us via Intercom - would be glad to help!💖

Did this answer your question?