I have added the JQL "fixVersion is not EMPTY AND project in (IT, DevOps) and status in (open, "In Progress", Reopened, Resolved)" to our Kanban Board to see all the JIRA Issues including the ones released. However I still cannot see the reopened issues with the fixversions on it under the AGILE-KANBAN BOARD-Only MY Open Issues?????
What should I do ?
Ok, that might be a factor later, but we need to see the *whole* board filter. Go to the board, click "board" to get to the config menu, then "configuration", and go to the "general" page. What does that page say for: * Filter Query * Kanban board sub-filter
Neither, they are perfectly correct and valid filters for using Kanban as it is intended. To expand on that... The board filter says "Look at these three projects" - that's clear and a really good choice of filter The Kanban filter says "Fix version is unreleased, or not set" - that is exactly what Kanban should do. Now, your stated problem is "I still cannot see the reopened issues with the fixversions". That is because they still have a fixVersion, and it is one that you have *released*. The filters correctly remove it. The next question is "does your re-open transition clear out the fixVersion field?" If it does not, then that's the problem!
Not really, because it will mean your Kanban board "release" function will stop working. You'll never be able to "release" the issues on the board,. That's ok if you're only using the board for reporting functions. But if you do this, it will mean the "done" column will grow to the point of uselessness.
Your swimlane isn't working because it only results in one data set which is the same as your board already covers. A swimlane does not change what the board selects, it simply divides the existing selection up into groups. The core of your problem is that you are trying to say "show me stuff that I have told you I don't want to see because I'm using a Kanban board". It's your data and process combined with the way Kanban works that is the problem, not your filtering. The best solution for this case is for you to use Kanban as intended - accept that having a fix Version that is released on an issue means it will NOT appear on the board. Adjust your processes to work with that. The other work-around is to change what you define as "done" in Kanban - change the Kanban board sub-filter to allow what you want on the board and exclude what you define as "done". For example, changing it to "customfield_done = empty" would solve the problem. BUT, it means you can no longer use the Kanban board "release" function - you will have to manually set the custom field.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs