TankType filtering and #3
Closed
rodeo wants to merge 0 commit into
Closed
Conversation
Contributor
|
Hello! Thanks for this! The bug with the duplicate filter entries was fixed in e6adaa4 and went out in the 1.2.0 release. This fix basically collapses types with the same name down to a single entry in the filter panel. Hope it makes sense in the context of your pipeline! |
Contributor
|
Thanks for the idea of controlling the link field ( 9022f45 ) -- this is very interesting! I think this is a very cool idea and will create a ticket on our end to make sure we pull this in at some point soon. It feels like a really useful feature for advanced customization! Thanks!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello !
When using the "TankType" entity (which is project-specific), the loader displays all the types from any project, causing an extra long and confusing list of possible filters. So this adds filtering on the context's project.
Also, we want to be able to display publishes grouped by a custom field on the publish entity, but the filtering is hard-coded to filter on the "entity" or "task" field. This adds the flexibility to filter/group publishes by any field, through an additional "publish_field" setting (default still is "entity"). As an example, a "By User" tab is declared in the "entities" default value.
Thanks !
Carine