But there may not be a proper queue. I have a number of issues which show up for a module I wrote which is an input filter. For instance, someone who wants to be able to link into collapsed fieldsets. It isn't something that I can fix -- it's not that I "won't" fix it, it's not my fault or problem. But it isn't either that the module is working as designed -- the issue isn't anything to do with the design of the module either... I'll try looking at the webmaster's queue, as this issue is more about the particular workflow on Drupal, not per se to do with the project module. Thanks, Ricky On Jul 27, 2012, at 1:55 PM, Ms. Nancy Wichmann wrote:

IIRC, there is an issue in the Project module queue. But it might be on the Webmasters queue.

The better approach is to move the issue to the proper queue rather than killing it. You can do that in the project autocomplete box where you enter update comments.

Nancy

Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

...

________________________________ From: "Morse, Richard E.MGH"

Hi! Where is the proper place to suggest adding a new issue status of "Closed (not my problem)" (or similar) -- this would be for issues which are not related to the project -- things like WYSIWYG editors adding a paragraph when a blank line is entered (for a project that has nothing to do with the WYSIWYG editor) or other such support requests that aren't really issues for the project they are submitted to...

The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

This kind of issue comes up for me a lot in @font-your-face, which interfaces with many remote services. When those services have problems, people open issues for the module, and they're issues I can't really resolve. I handle this by changing the issues (which are generally opened as bug reports) to support requests, offering the support I can, i.e. a short explanation, and marking them fixed. That works well in my experience, so I don't personally see a need for a new issue status. But if you do, I think the best place to request that is the project_issue module, in which the statuses are defined: http://drupalcode.org/project/project_issue.git/blob/refs/heads/6.x-1.x:/iss... -- Scott Reynen Sliced Bread Labs On 7/27/12 12:23 PM, Morse, Richard E.MGH wrote:

But there may not be a proper queue. I have a number of issues which show up for a module I wrote which is an input filter. For instance, someone who wants to be able to link into collapsed fieldsets. It isn't something that I can fix -- it's not that I "won't" fix it, it's not my fault or problem. But it isn't either that the module is working as designed -- the issue isn't anything to do with the design of the module either...

I'll try looking at the webmaster's queue, as this issue is more about the particular workflow on Drupal, not per se to do with the project module.

Thanks, Ricky