Closed (duplicate)
Project:
Storm
Version:
6.x-1.x-dev
Component:
Storm Attribute
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jul 2010 at 19:21 UTC
Updated:
13 Oct 2010 at 20:54 UTC
When trying to edit the attributes for project status search, I am unable to add to the key (but am able to DELETE from the key). Haven't messed with other keys or looked at code but noticed this bug on the project status OPEN attribute.
Also, another thing that could be discussed, is a way to connect Status and Status search, instead of them being so independent (when in fact one is the search of the other)
Comments
Comment #1
JGonzalez commentedI'm dyslexic.
Comment #2
juliangb commentedThe key is character limited, Im not sure if this is what youve experienced. It is just so that the key fits in the database field.
The whole attributes system really should become part of admin settings pages imo...
Comment #3
JGonzalez commentedI thought that it was char limited, but this was not the case. I could delete as many characters as I wanted, even delete it all, but was not able to type anything back into it. Will look into it more.
I think a revamp of attributes system would be a way to go, but I imagine the overhaul would be extensive.
Comment #4
juliangb commentedAh, not sure then.
I´d imagine the overhaul would be by domain, so could be done in stages. Any ideas for the best method?
Comment #5
tchurch commentedI think there's some issue with the online add/edit form for attributes.
If I try and update the task status search "open" to add another value I can only type 20 characters into the key box (even if it already contains more than this).
And the value box takes over 100 character (118 I think) which is more than the DB can hold.
Comment #6
juliangb commentedRe #5, see 899970. There is an easy patch there that needs completing to solve this.
Comment #7
JGonzalez commentedRegarding #4,
As for a start to this, I think we should find a way to phase out the "SEARCH" attribute domains. This alone would simplify the attributes in almost half.
For example: For PROJECT attributes, you have "Project Status Search" and "Project Status". As far as I understand, the "project status search" is used for the ability to filter by. What use cases are there for having a different search status than all the statuses? Would it be possible to remove all the "NODE-TYPE KEY SEARCH" and only use the "NODE-TYPE KEY"
So, "PROJECT STATUS SEARCH" would no longer exist, and storm would just use the values from "PROJECT STATUS" in the filter by. The same could be done "PROJECT CATEGORY SEARCH" and "PROJECT CATEGORY" etc etc. This should reduce some of the redundancy of duplicated values. The only place I see the "SEARCH" items valid are for grouped items with multiple keys ("completed", "open")
Comment #8
juliangb commentedThis conversation is best continued at #532420: Change attributes into taxonomy