Jira & Maintenance

Every Monday at Numiko, a handful of the team are selected and are assigned Maintenance tasks to complete. This could be fixing a bug, changing text colours or resizing an image.

Me and Michelle have been given the role of ‘Testers’ for Maintenance Mondays, and once a task has been completed, it is then passed to either myself or Michelle to be tested.

There are many types of testing we have done including: Cross-Browser, Cross-Device and Security. For Cross-Browser and Cross-Device testing, we use the physical device where we can but if this is unavailable we use Browserstack which allows you to virtually use various Devices and Operating Systems.



Numiko use Jira to organise and assign tickets around the office. Jira Sprints feature a ‘To Do’, ‘In Progress’, ‘In QA’, ‘Done’ and ‘Approved’ columns. When testing a ticket on Maintenance Mondays, me and Michelle follow the procedure of commenting on the ticket and moving it from the ‘QA’ column and into the ‘Done’ column, dependent whether it works as expected or not. We then assign the ticket back to the Project Manager.

If a ticket isn’t working as expected, we are then given the chance to suggest a way it can be fixed. Each member who works on a ticket in Jira, logs their time on how long they have been working on it. This allows the Project Manager to see how well the project is progressing and if they are staying within Budget.

A ticket in Jira, can be created by anyone who has access to Numiko’s Jira. This can involve Clients, Project Managers and other Developers.

When creating a ticket, you first specify what type of Issue the ticket is for. This could be a Task, Improvement or Bug. You then enter a short summary which works as a title for the ticket. After this, you enter a Description of the issue. This should be as detailed as possible, explaining Device, Operating System and Browser so other Developers can replicate this issue to find a fix.

You can then link the ticket to a specific account, so when time is logged by a Developer, it will be logged to that account. After this, you can then create an estimate – this is usually done by Project Managers or Developers when having a Sprint Planning meeting, this is where you aim to keep in the budget of the project.

Then you select the priority of the ticket, this can be Minor, Major or Critical. This can help Developers prioritize their tickets. A Page URL and Image Attachment can be useful on a ticket, is this can show a Developer exactly what and where they need to fix. After this, you can assign the ticket to a particular developer, or allow Jira to automatically select one for you.