Closed (fixed)
Project:
Project issue tracking
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 May 2012 at 23:32 UTC
Updated:
4 Jan 2014 at 02:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
senpai commentedAssigning and tagging.
Comment #2
dwwActually, change of plan. We still need this setting for #1044950: Re-architect the project-dropdown UI selector on node/add/project-issue to prevent server crashes, although maybe it should just live in project itself? It'd be shared with both project_issue and project_release that way (since we also have the same UI problem at node/add/project-release, although d.o doesn't expose that page).
I suppose this could still be a node-type setting instead of site-wide. However, maybe that's overkill, and we could just get away with a site-wide global for this.
There's also a somewhat wonky "Project navigation" block that d.o doesn't use, but that'd care about the same thing. Another reason to just have this in project (if we keep that functionality at all).
Comment #3
senpai commentedComment #4
iamcarrico commentedI am taking over this from mister Ristroph... will take a look today.
Comment #5
iamcarrico commentedOkay, this just removes the old setting, and moves it into the new location (the project module). Text might want to change a wee bit, but works good.
Comment #6
dwwCan you explain your reasoning here? I'm not sure it makes sense to have this per-project-node-type. You combined two half-baked proposals of mine into a single cake that doesn't seem like it's going to work at all. ;) For example, /node/add/project-issue is potentially including choices across multiple project node types. It's a single UI. I fail to see how we can reconcile a setting on each of those project types to figure out the UI to use. Seems like a mess.
Either this needs to be a setting tied to the [project-issue] node type in the URL, or it needs to be a global site-wide default. But a setting tied to each project type seems like the worst of both worlds. ;)
Also, just moving the setting around doesn't actually give us the autocomplete, etc. This issue is about porting the functionality, not just the setting UI itself.
Edit: see comment #8.Thanks,
-Derek
Comment #7
senpai commentedTagging for Sprint 4.
Comment #8
dwwNote: I forgot we already had #1044950: Re-architect the project-dropdown UI selector on node/add/project-issue to prevent server crashes open about using this setting to control the UI at node/add/[issue-node-types] so we can leave that part out of the patch here.
Comment #8.0
senpai commentedLinking to #1044950
Comment #9
iamcarrico commentedOkay, the project_issue patch from comment $5 is still 100% accurate. I am also including a patch for projet that will create a settings page, as well as this lonely setting here.
Comment #10
iamcarrico commentedComment #11
dwwCommitted/pushed #5 to project_issue.
Cleaned up the titles and descriptions of the menu items a bit (Sentence case instead of Always Caps, etc) and committed/pushed #9 to project.
Thanks, and sorry for the delays!
-Derek
Comment #12
iamcarrico commentedComment #13.0
(not verified) commentedClosing the h3 tag.