Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta should application wide or project wide ? #10

Closed
TheCloud opened this issue Sep 16, 2018 · 13 comments
Closed

Meta should application wide or project wide ? #10

TheCloud opened this issue Sep 16, 2018 · 13 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@TheCloud
Copy link
Contributor

Currently only Kanboard admins can add new meta fields, and when admin do so, all projects's tasks are affected.

I think that a Project Owner should have the same functionality but "project wide" only, in this way only his project's tasks are affected.

So basically you can have:
=> Application wide task's metadata
=> Project wide task's metadata

Please note that it's always about tasks's metadata that I'm referring to, not project's metadata or user's metadata

@TheCloud TheCloud added enhancement New feature or request question Further information is requested labels Sep 16, 2018
@creecros
Copy link
Owner

Yes, this would be nice, but would take a lot of code alteration I believe, not even 100% sure it's feasible without creating a table, because meta data table has basically three fields, id, name and value. I'd have to look into it.

@creecros
Copy link
Owner

To explain, there isn't a field to hold a project_id

@TheCloud
Copy link
Contributor Author

Yes I noticed that there isn’t a project_is anywhere.

We could just alter the current tables - if no project I’d is specified, it’s application wide. If it’s specified it’s project wide

I will think about it, for now let’s keep it in mind

@creecros
Copy link
Owner

I think for now, I'm good on this. It will be a lot of work to put this in, something I could perhaps revisit later down the road. I'll leave this open as a reminder.

@creecros
Copy link
Owner

creecros commented Nov 5, 2018

more notes

  • the settings panel would never be accessible to anyone that isn't an admin, so a new config menu would have to be added into projects config.

  • 'human_name' cannot be duplicated, or there would be issues, admin set fields would have to take priority.

  • add project_id to metadata types table

@tjdm007
Copy link

tjdm007 commented Nov 21, 2018

After installing the update, 0.0.8 the screen is empty / blank.
did I forget something?

@tjdm007
Copy link

tjdm007 commented Nov 21, 2018

I understood. the metada extension is incompatible.
I deleted it and everything is ok ..

@creecros
Copy link
Owner

Moved to separate issue #29

@Ryonez
Copy link

Ryonez commented Jun 25, 2019

Defiantly would like to see this. Currently while nice, I can't use it because I plan to have projects that wouldn't make sense to have fields from all the others.

@creecros
Copy link
Owner

Its been requested a few times, and its on my long list of to dos.

@Ryonez
Copy link

Ryonez commented Jun 25, 2019

They never seems to end do they...

It's all good though, I'll keep an eye out for updates, cheers.

@creecros
Copy link
Owner

Was easier than i anticipated.

@Ryonez
Copy link

Ryonez commented Jun 28, 2019

Was easier than i anticipated.

Good to hear, thank you for adding that in!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants