issues

Apologies in advance for this crossposting to 11 groups. I recently started an issue to help us get to know each other better: Add field for "Memberships in Associations, Societies, and Other Professional Organizations" to User Profile. The initial response was, "Don't see why not, but let's hear more support before we do." So this is an appeal to read the issue and consider giving it your support.

I've created a javascript which adds plain-text links to issues for easy copy / paste into issue comments. For information, see the handbook page. But this brings up a topic for the redesign - what functions or features are missing which would be useful to developers? I'm sure many of them belong in project.module, but obviously how they are implemented would affect the redesign :)

I've been evaluating solutions for Project management (for the duration of this post, that includes what i describe as project, issue, ticketing, case tracking, and pretty much anything that falls in that category) solutions with Drupal, over a year actually. I keep being enticed by the features of each individual solution, and new promises that are announced for each module(s) and trying them out and coming to the same conclusion with each of them. And yes, all of them seem to have the same problems that I'm hitting repeatedly.

Hi there, I have been scouring the support forums for something about Zen block settings for subthemes in a multi-theme environment but nothing yet.

Can anyone here verify that you can run Zen and Zen-fixed and configure block differently for each of the themes?

I have created an interesting environment an an attempt to share some assets between the subthemes I have made. Sort of like Zen sub theme families.

for my issue tracking needs at my day job (http://www.cs.wisc.edu/condor), we'd like to start keeping track of how long we spend on a given issue. mostly, we'd use this for our internal development tasks, not so much the "helpdesk" style end-user support (though i could see us caring about time spent in those issues, too).

clearly, this is something a lot of issue tracking systems already support, and lots of people need this kind of functionality (though often in more corporate environments). however, i'm not sure we'd want anything like this in the issue queues for drupal.org (though i'm not really sure... i could potentially see it being useful, even there, though for different reasons). generally, i'm leaning away from wanting to have any of this functionality on drupal.org.

there's are a few issues in the project module's queue (http://drupal.org/node/44162 and some duplicates), about how to link different issues together and record relationships between issues. so far, we've been talking about issues from the project module, but the ideas are generally applicable. i thought people interested in the issue tracking and relationships groups might have ideas. a few potential use cases:

1) recording the duplicate issue id so that a) we can automatically add a comment to the "parent" issue that another duplicate was just created (which bumps the issue's access time, since effectively the duplicate means another instance of the issue was just noticed), b) we could have a block of links in the parent that showed all the duplicates, and c) we have a consistent way to display the parent issue inside the child...

I guess this is the place to talk about "issues" - :). First off - Moshe - you totally ROCK! :).

Yesterday when I tried to upload a file (.png) in the events group the file wouldn't "take" - it just won't upload. When I tried to report this in the issue tracker I got to the content creation screen but there a) wasn't a "tracker" content type and/or it wasn't clear how to categorize the issue so that it would go to the right place.

Under "Feedback" at http://groups.drupal.org/helloworld, the following is stated:

The site has a simple ticketing system for reporting issues. We hope to soon provide each group with its own ticketing area. We also have a feedback form -http://groups.drupal.org/contact.

When I click on simple ticketing system for reporting issues, it shows me the 6 issues submitted thus far. (7 issues total as of 5/7/06, but one of them is a duplicate so really only 6 issues.)

So far so good.

However, when I get to the simple ticketing system screen and try to add a new case, I don't see a way to submit my issue.