Epilogue Being a software developer I were not worried much about an issue’s status after finally clicking on the so desired “Resolve” button in an issue tracker software. Let’s skip all pathetic words about “personal responsibility” for the delivering production ready and tested functionality – at some point the developer’s responsibility is over and either an end-user will work with it or, that it’s much better, a QA team start verifying the just developed of fixed functionality. However, becoming a Project Manager I were forced to look deeper and be aware of the status of each issue (story, task, bug etc.) until the moment of deployment it on all existing environments: testing, staging and production and it is the place where the problems start appearing. Introduction Atlassian Jira has already become the de facto standard for many projects, although appliance of it in real projects causes difficulties and attempts to map real project's processes to simple workflows. ...