I should like to advance our team culture by introducing Kanban to a team of (non agile) Business Analysts (BA). All of them (currently there are nine BAs) work on (non agile and agile) projects.
My starting point would be
What steps I've already taken:
Objective:
Questions:
Can this be done with out of the box Kanban boards? Our on premise installation is fairly restrictive when it comes to adding plugins etc.
project in (your projects business analysts work in separated by commas) and assignee in (username of your Analyst separated by comma)
Cheers.
Thank you for your reply, and apologies for the lack of clarity w.r.t. my second question. "Contributions" refer to the user's
The first aspect can be covered by your helpful suggestion #1 above. How to cover the other three aspects is more difficult (at least for me).
To add one more aspect to my initial question, the view of the Kanban board should be limited to only those items that were commented on, assigned to another user or solved within the last week.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Aaron Rothschild ,
With the second the statement gets a lot more complicated because you are looking for various potential options that I cannot think of how to handle easily.
You will need the add-on scriptrunner because of the JQL functions it provides that lets us search by who commented on the issue.
Your JQL will be something like:
(assignee in (List of your team separated by commas)) OR ((issueFunction in commented("by user1") OR issueFunction in commented("by user2") ..... OR issueFunction in commented("by userN")) AND issuetype in (Task, Story, Epic)) OR (status changed to "Your resolution status" by "your user")
The one entry I am unaware of how to fetch is assigning an item to another user (when you say solving, I assume the user transitions the issue status else there is no way JIRA can tell if he just adds a comment that helps to solve the issue.)
The part about assigned, e.t.c in the last week would be tricky to implement as JIRA just has an updated date not specific date to mark date ticket is assigned, e.t.c.
Hope this helps get you started.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.