Re: [xwiki-devs] [Proposal] JIRA strategy for issues we don't plan to fix (SUMMARY)

Hi, I mean when I know there is no Jira issue at all, as the problem didn't arise in any of the previous releases. The problem only arises on a version that hasn't been released. In this case: - There is no Jira issue to reopen or comment on - I cannot open a new bug on Jira (the rules say if the version has not been released then I shouldn't create a new JIRA issue for reporting the problem)

vmassol wrote: > > > On Feb 2, 2010, at 2:12 PM, Silvia Rusu wrote: > >> >> Hi, >> >> Here's an excerpt from the set of rules about not creating issues for >> unreleased work: >> >> "Imagine that someone has been working on a given issue for a given >> version. >> Then someone else notices a problem related to the work done. If the >> version >> has not been released then you shouldn't create a new JIRA issue for >> reporting the problem. Instead you should reopen the issue (if it's been >> closed) and add a comment to it." >> >> There should be a mention about what to do when you encounter a problem >> for >> which there is no Jira issue. > > You mean when you don't know if there's already a jira issue or not? > > Yes sometimes it's hard to know (especially if you're not a developer and > thus not following the devs that happen). In this case you can just create > an issue and the person responsible for it will close it as duplicate for > ex and thus set the "fix for" to "unknown". > > Is that what you mean? > > Thanks > -Vincent > >> >> For example the way I report this is by creating a page on the incubator >> in >> the "Test" space. There I present the issue, attach printscreens and >> mention >> the version where I encountered the problem. >> If the problem is not fixed in the release I report it on Jira. >> >> Is there a "standard" procedure for this type of situation?