Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Boosting team's visibility with ScriptRunner like a boss

Just like almost every team here we are struggling with visibility both internal and external each day. I want to share a short story about how we have improved the internal part by a great deal and probably the external part by a bit too.

It has all started on one of our retros where we were discussing low morale in the team and how it may be affected by issues with internal visibility especially when some of the team members are working from home or have a meeting colliding with the standup. We then started discussing on how we can improve it: maybe with posting our stand-ups in the teams room on our communicator or having a Trello board for our stand-ups/more granular reports but... hey... why not use Jira for that?

We've also discussed some things that worked and helped and we knew for a fact that having our board displayed during the stand-up helps greatly. But what about people who can't attend? Well, they could just update their Jira issues like everybody else would. Great, now how do we make that information visible? Jira can display custom field's value on board's cards so we only need a custom field that would have an auto-calculated value of last comment. ScriptRunner's Scripted Fields to the rescue:

Screen Shot 2018-06-13 at 11.42.34.jpg

We are hoping this improvement will also make our stand-ups more task oriented and less people (assignees) oriented.

And now some after-credits.:

With ScriptRunner's issue JQL function we were able to craft some custom JQLs that help us with the process eg. list of current sprint's issues assigned to current user that are in progress and weren't updated for more than 24 hours. We then created a new dashboard that would display different sets of issues from the current sprint:

Screen Shot 2018-06-13 at 11.56.41.jpg 

But then another eureka moment came. We can have custom card colours on our board! So why not just colour the cards that need an update? (Issues that need an update are coloured in orange)

Screen Shot 2018-06-13 at 12.12.00.jpg



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events