Hello,
We are trying to find a way to make a second level grouping of the projects. The first one is used with the categories. We need to to make difference between two projects with same category but with different project schemes or some other criteria. The purpose is to do it at a Project level.
BR
Mario
We have managed to find a solution using third party app from atlassian.
Thank you all for the support.
BR
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are not many options to make this happen as there are very few things you can 'customize' within a project. I've thought of two options;
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your answer @Daryl Marsh
Unfortunately neither of the ways can be used to filter by. If we want to filter them by some way or exclude such projects from automations or subscriptions there is no way to do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The filter would include (description ~ "your word")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We want to filter them at a project level, not task level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Mario Nikolov
Project categories are not tied with the project configurations. It's just a placeholder for better filtering. On a project level, I would suggest using components that will group more issues into one place. Use filters that are referring to these two projects based on criteria that matches your use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Nikola Perisic ,
Thank you for you response!
The goal is to have two different things to filter by on a project level. The category the first one and something other for the second criteria.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To understand this more clearly, this is for one project that needs to have different categorization criterias?
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.
You can add a category per project. Workaround would be to group different projects under same category and then create a filter. Not the other way around.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have got here. But after two different types of projects are under one category we need another way to filter which projects are Type A from the category and which Type B. This should be done at a project level. Case scenario like using the Jira Filters to select the category and to filter them through the tasks in them is not the desired goal.
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.