Is this a question or an error. Maybe it’s an improvement request.

Submitted by Lennart Kats on 8 July 2011 at 17:19

Yup, that’s right. Developers are free in choosing what types of issues they want. I also allow them not to have types. Does this pose a problem?

For a recent issue I submitted, I forgot to set the type: researchr/270. I wanted to set it to ‘question’, but the system didn’t tell me that I forgot to set it and also wouldn’t allow me to change it afterwards using ‘edit issue’ :o

Tags are always the key in YellowGrass :p Issue types are just meta-tagged tags. To turn an issue into a question, just tag it ‘question’.

Yeah, I realize that. But I don’t have the right permissions to set tags in the researchr project :o)

Ah no, you cannot do this in projects you are not a member of. YellowGrass issues are a ‘fire and forget’ principle. Once submitted you should not try to meddle with things anymore. If the project is not yours, you pass the responsibility on to the developers.

Now, I know that one can edit issues after submission. This breaks the principle and may be somewhat confusing. I guess it should be disabled. But of course this won’t solve your issue, only make clearer that what you desire is not supposed to be supported.

I edit issues all the time, fixing minor mistakes or omissions :) The one linked here I edited to fix the link. And if I could I would have added that question tag that I forgot.

Yeah, I do that too. That’s why editing an issue is possible even when one is not a project member. Yet, it is dangerous. Issues must not be changed by non-project members while they are being fixed. There should be some mechanism that should allow the submitter to change mistakes, yet that prevents changes once the issue has started to be processed by developers. Not sure what. Maybe a timing mechanism. I need to think about this. If you have ideas, let me know.

I do not know a solution now. Marking it for a future release.

Does not fit in the yellowgrass interaction model. Won’t fix.