How can I allow others to edit my filter that are added to my Kanban board?

[Jadiam Lopez]

Community,

I am not very well versed with Jira and the little I know how to do is by trial and error.  I was able to create a filter where I place all of our issues for dev which shows in our Kanban board.

My question is how can I allow another member to have permission to edit my board, as when I am away on vacation no one is able to update the Kanban board when we need a ticket added or removed from the board.

[Jack Brickey · Accepted solution]

board administration is singularly owned in cloud. you can change the owner of shared filters/dashboards under admin > system > shared items

[Jack Brickey]

Oh my.... I don't think that is what you want for a filter. Is there a reason why you have listed out the specific issues here??

maybe something like "Project = IGDEV" would suffice?

[Trudy Claspill · Accepted solution]

Hello @Jadiam Lopez 

Welcome to the community.

Can you show us the filter you have created for your board?

There should be a way to construct a filter for your board so that the issues will show on the board automatically based on criteria, rather than requiring a change to the filter for each new issue.

[Jadiam Lopez]

@Trudy Claspill 

For some reason I am not allowed to show a print screen.

[Trudy Claspill]

So, in your filter you are specifying the project and then a list of specific issues. Is there some setting that all those issues have in common that could be used instead of listing them individually? 

I see that your filter name is "High Priority Items". Can you change the filter to instead be

project=IGDEV and Priority=<VALUE>

...where <VALUE> is the name assigned to Priority for High Priority issues?

Then your board would include all issues from the IGDEV project that are High Priority, without you have to provide an explicit list of issues. As any issue in the project has its Priority field set to High, that issue would then start showing on your board. If the Priority field was changed to a different value, it would stop showing on the board.

[Jadiam Lopez]

Trudy,

thank you for your time, as for our filter, it's titled as such but all tickets within the filter are tickets that dev needs to review or can manage via the Kanban board.

I can change the name of the filter to Igea ticket items, but what I really need is to allow someone else to add the new tickets that are created to the board, and to be able to remove the tickets from the kanboard when they are completed and deployed in production.

Not sure if we are using the Kanboard correctly, but once a ticket is completed (done), we have to check with the client to make sure the issues were resolved, if they are, we can then remove from the kanboard, which is why I have the filter setup this way.

But if there is a better way to have all tickets added to the board, and a better way to remove a ticket from the board when we know the fix was a success in production I am all ears.

I was trying to contact Jira customer support but I have not had any luck with reaching them.

[Trudy Claspill]

Hello @Jadiam Lopez 

Since you are using the Free Plan (according to this post) you are not entitled to support from Atlassian.

Because you are providing a specific list of tickets that leads me to think that you are not wanting to show all the issues in the IGDEV project on the board. Is that correct? Does your dev team need to "review or manage" only some of the issues in the IGDEV project? Or do all issues in the IGDEV project get managed in this board?

If all the issues in the project are managed by this team, then there is no reason to have a list of issues as part of your filter.

If all issues in the project require validation by the customer, then they should not be set to Done until that has been completed.

Are you using the Release/Fix Version functionality of JIRA?

If you want only a subset of issues in the IGDEV project to be visible on the board, then I recommend that you find another way to identify the issues that need to be included in the board. You could add a value to the Components field or the Labels field for each issue that needs to be included on the board, and then change your filter to look for that value. Then the issue displaying would be managed by changing the issue, not changing the filter.

[Jadiam Lopez]

@Trudy Claspill 

I was told we upgraded recently, so I should have support now, as the owner had to upgrade from free due to documents we uploaded to confluence.

Prior to our changes only some of the tickets needed to be on the board, but we learned that a lot of tickets were not worked, so now we need all tickets to be listed on the kanboard.

For tickets that require a new version we are using the Release/Fix Version functionality of JIRA, but some tickets do not require a new version.

Ideally, I will like to have all ticket that I create in Jira to automatically land on the board, and when they are placed as "done" they will automatically be removed from the board.  

[Trudy Claspill]

If you want all issues in the IGDEV project to appear on your board then set the filter to 

project=IGDEV

Then all the issues in the project will show on the board. You won't need to create a list of issues as part of your filter.

Typically on a Kanban board there is also a sub-filter, which you would see in Board Settings > General at the bottom of the screen

When you are using Releases/Fix Version, at some point you should be going to the Releases page and updating each Version to have a status of Released, with a Release Date.

 For the issues where you fill in Fix Version the issues will display on your board until the associated Release/Fix Version has been set to Released. When you make that update on the Releases page, the associated issues will stop displaying on your board. You don't need to maintain a list of issues in your filter to "remove" issues from the board in that scenario.

For issues that don't get a Fix Version, those will remain in the right-most column of your board until they have been there for as long as or longer than the item in the image above labeled "Hide completed issues older than". The smallest amount of time you can set that to is 1 week. So, again, the issues will automatically stop displaying on your board and there is no reason to maintain a list of issues as part of your filter.

I'm not seeing a reason that you need to be creating an explicit issue list as part of your filter. Am I missing something about your scenario?

[Jadiam Lopez]

Awesome advice, this will help me.

I appreciate you!  Have an amazing week!