confirmed

we are evaluating the permissions and looking for a solution.

reassigning to support.
This behaviour is a result of giving "Registered User" the "Project Issue
Change" permission.

I've filed an internal issue for the engineers to review, investigate and
restore the functionality. I will update this issue when they have commented in
the internal one. Thanks

I had previously filed PCN 24809, asking CN to clarify the prior IZ permissions.
louis

This issue is undergoing investigation by the inst engineers. I will update this
issue when the internal one has been updated.

the internal team is still reviewing this issue. I will have a more substantial
update by monday

1. Registered Users can submit issues and the default state is UNCONFIRMED.  
2. Registered Users can modify issues to be able to add attachments and vote.
3. Only a certain set of users can change the state from UNCONFIRMED to NEW.

for clarification the Product Management asks:
The question for the OpenOffice folks is whether they can work with #1 and #2, 
or with #1 and #3, or must they have all 3 of these conditions at the same 
time?

>1. Registered Users can submit issues and the default state is UNCONFIRMED.  
>2. Registered Users can modify issues to be able to add attachments and vote.
>3. Only a certain set of users can change the state from UNCONFIRMED to NEW.


>for clarification the Product Management asks:
>The question for the OpenOffice folks is whether they can work with #1 and #2, 
>or with #1 and #3, or must they have all 3 of these conditions at the same 
>time?
obviously we need all of the three issue. As a possibilty I can imagine to part
#2 into two parts:
2a. Registered Users can modify issues to be able to add attachments.
2b. Registered Users can modify issues to be able to vote.

2a. is essential to have.
2b. we do not rely of voting at this time.

if it is possible to enable #1, #2a and #3 in short term this would help a lot.
as #2b is a desired feature we would expect a plan when full functionality will
 be available again.

After doing some research, CN has taken the feedback and will be incorporating
the necessary changes to the live site via a patch.

Currently OOo is testing things on a staging server and is providing feedback to
CN via Louis and Drew. 

There was a bit of confusion last night and today about IZ permissions after a
change to the live site made it appear that both the live and staging sites had
both gone live with a finished change, which they have not. OOo has revoked a
role  on the live site which enables them to do the necessary research on the
stage site and comparisons to the live site. 

Martin commented to Drew after reviewing some of the workflow on the stage site
that:
  further testing of the staging server shows, that we still not have what we want:

if "registered user can change issues" is off, new issues by unprived 
user are submitted as UNCONFIRMED, they can do attachments, vote on it 
but not comment on these issues.

if "registered user can change issues" in enables, new issues will be 
submitted as NEW again,

so we still not have the disired behavior on the staging server.

--
These comments have been added to the internal issue.

This was done last week. The internal issue has been marked resolved/fixed.
Unconfirmed is the initial state.

Resolved. OK.
But owner of issue can't close (duplicate or invalid) or reopen his issue.
Didn't got this problem before the last year issuezilla update.

Maybe I'll open an issue for this problem.

Ooooppps.

Forget my last comment.

Mistaken with another issue.

verified and closing

I want to reopen this issue.
Today I filled the issue 62086 and the initial state was NEW.
Unless qa members (with 'canconfirm' "powers") can insert issues as NEW.

Thank you.

Hwoarang

Sorry, my last comment, I didn't see that there's two initial states to choose
when filling a new issue.

Hwoarang

closing again.

hmmm...
but 'UNCONFIRMED' should be the default state, even with two option there.

Hwoarang