Skip to main content

January 3

To date I have

Cleaned up a SharePoint data share for consistency around projects

Migrated multiple teams into a new Jira project

Created new Scrum boards and SOS boards for all those moved teams

Created a first stab at an overview board so one can see all in progress, upcoming, and backlog work - with filters for teams

Have been managing Jira (workflow, post-status functions) and I need to learn more to accomplish more. I current setup anything going to status "completed" gets resolution: done and "rejected" gets "won't do" to help with built in default reports, dashboard items and reporting.

Decided I must learn to write Jira reports and Dashboard widgets to remove wasted redundant weekly work on writing reports and status updates - when all the data should be in Jira.

I'm still trying to get a handle on everything but my goal I was given was
1. Visibility into what we are doing and need to do
2. Ability to estimate upcoming requests (this gets into creating templates, automation, processes)

My person objective on top of the above is to remove as much wasted time (duplicate work, non value added work) from team members as I can.
Specifically I want them to log hours in jira, but in return provide them a weekly pay report to input to the pay system, and a weekly status report to provide to their manager (adding comments). I want scrum masters to be able to have reports on epics, and sprints, be self service and self evident. I also would like sprint planning (allotment of hours per person, even cross team) to also be available as a tool for scrum masters, and a report visible at a whole group level as well.

I need to now clean the migrated Jira backlog and get it into a semblance of compliance and iterate on the fields and statuses.

I also need to get ready for the upcoming sprint, Grooming did not go smoothly this time, or last time.

I also need to get everything to stop being in emails, and unique - repeatable (documented!) processes!

Comments

Post a Comment

Popular posts from this blog

How do I find the Custom Field ID in Jira Cloud?

So you need to find the Custom Field ID in Jira Cloud. Perhaps you need the ID for a custom field to work on soem code, an API call or a script. How do you find it? You can find the ID in the URL when managing custom fields Jira - Settings - Issues - Fields - Custom Fields https://***.atlassian.net/secure/admin/ViewCustomFields.jspa Select "Edit" on the desired custom field .../admin/EditCustomField!default.jspa?id=12802 There you go! It is that number at the end of the URL Alternately, you can use ScriptRunner Jira - Setttings - Add-ons - Script Runner - Script Console and run the following def issueKey = '***-####' def result = get('/rest/api/2/issue/' + issueKey)         .header('Content-Type', 'application/json')         .asObject(Map) if (result.status == 200){     return result.body.fields } else {     return "Failed to find issue: Status: ${result.status} ${result....
Post a Comment
Read more

The dreaded "Clone" in Jira

Jira Cloud Scrum Teams Case: We clone template issues, as our work is repetitive, and get “clone” in the summary and it makes it hard to read. Built-In Jira allows you to remove "Clone" from the story you are cloning, but if you are also copying the sub-tasks there is not the option to remove it. There are ways to turn this off in Jira Server, but I could not find it in Jira cloud. Solution: Jira - Settings - Add-Ons - ScriptRunner - Escalation Service The Escalation Service called: Remove Clone In Summary As this user: (myself) Checked - enabled On this schedule: Every Hour For first 50 results returned by this query:  Project in (pipe) and Summary ~ "CLONE" Will run this code:  // check if issue.fields.summary looks like "CLONE -" def updatedSummary ="" if (issue.fields.summary.startsWith("CLONE -")) {     //if so, modify issue.fields.summary to not suck.     updatedSummary = issue.fields.summar...
Post a Comment
Read more

Jira Administration

Some things I have setup in Jira to make life better for me, with the way we work. Use Case 1: You should not close a story when sub tasks are not complete How? Jira - Workflow - Edit Transition Condition, before allowing a story to Status Category Done "All sub-tasks must have one of the following statuses to allow parent issue transitions:" (All done statuses) Use Case 2: You should not close a story until the blocker or impediment is resolved. How? Jira - Workflow - Edit Transition Condition, before allowing a story to Status Category Done "Value Field" The field Flagged will have to be not equal to value '"Impediment"'. Compared as String. Use Case 3: Set resolution when completing an item. Why? If no resolution is set some reports and metrics don't calculate correctly. How? Jira - Workflow - Edit Transition Done Post Function, Status Category = Done JMWE The value(s) of field Resolution of the current...
Post a Comment
Read more