 September 14, 2007 - 2:38pm | Please do. Right now, I have a couple ideas about what you mean. |
 September 14, 2007 - 3:40pm | I'm assuming you mean a system like this one we're using now? I know drupal has that... but I don't know. It's a bit of work to duplicate this process and compartmentalize it. It may be possible to use this same system but let each issue have a hidden "Project" field that identifies it. I do that with the downloads system (I made one site-wide downloads system but each downloadable item has a "Project" field that can't be seen or changed). Maybe this would be a solution... But also the more ways in which we can comment other than the forums detracts the usefulness of those forums. Right now it's totally possible for someone to simply post a new forum topic and allow people to discuss it. Normally speaking, I don't think most projects would have a use for a "support issue queue" like this one. However, projects such as the Online Character Sheet will be a web-based thingie... and that I can see having support queues. I don't know, what do you all think? 3. We wear sungoggles during the day. Not because the sun affects our
vision, but when you're cool like us the sun shines all the time. |
September 14, 2007 - 3:58pm | Well, what I'm thinking he means is that he has some special programming planned for his new Random Planet-System Generator. If he had a support forum separate from the normal forum, he could isolate specific problems easier, leaving the regular forum available for idea generation and discussions of features and code. Though that's just a stab in the dark. I'm really not entirely sure what he wants. |
September 14, 2007 - 9:23pm | Well, what I'm thinking he means is that he has some special programming planned for his new Random Planet-System Generator. If he had a support forum separate from the normal forum, he could isolate specific problems easier, leaving the regular forum available for idea generation and discussions of features and code. Yes - I think that's what he wants.Though that's just a stab in the dark. I'm really not entirely sure what he wants. That kind of system would work well for some types of projects (such as the online character generator or the online planet/system generator). I'll see about it. 3. We wear sungoggles during the day. Not because the sun affects our
vision, but when you're cool like us the sun shines all the time. |
September 15, 2007 - 8:38am | I understand what your saying, need moore thought. I guess you could expand the current issue queue to including Project Name (autoselect) so that ppl can post specifics on broken site, or broken project. also, there is a way to embed another drupal site within a drupal site....to the client it's like one site, but behind the scene it's multiple sites. so for instance, say OCS broke, then it would not break sf.us  |
September 17, 2007 - 12:12am | that was a bunch o'work! Project Managers can go to the edit page for their project and there is a new option. "Use Support Issues" or "Do Not Use" support Issues. By default, they're turned off. If you want a support issue queue for your project, simply go turn the feature on. Once enabled, the support issue system will be just another tab at the top of your project, called "Support" - in addition, the project summary block as shown in the Projects page will include a link to the Support section of the project. Only project members are permitted to add support issues to your project's queue. Project Manager will be able to change the status and severity of an existing support issue by changing simple comboboxes when viewing an issue. These controls will not be available to anyone but the project manager (and a site referee). New/updated support issues will show in the "What's New" page and on the project's front page for users who are members of your project. They can of course be "Marked as Read" also. 3. We wear sungoggles during the day. Not because the sun affects our
vision, but when you're cool like us the sun shines all the time. |
