
| Key: |
MISC-1352
|
| Type: |
Meta Issue
|
| Status: |
Closed
|
| Resolution: |
Duplicate
|
| Priority: |
Nice to have
|
| Assignee: |
Unassigned
|
| Reporter: |
DR Dahlgren
|
| Votes: |
0
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
JIRA
|
|
Issue Links:
|
Duplicate
|
|
This issue duplicates:
|
|
WEB-382
Bugs and Proposals on the JIRA Should Not Be Closed Without the Author's Consent
|
|
|
|
|
|
|
|
The ability to close a JIRA post as resolved should only be available to Linden employee or the original poster. Just because some other resident does not like the post, or in their opinion it duplicates another post, or they think it is resolved, should NOT give them the ability to close a post. This ability to close another's post can easily result in abuse and should be removed.
DRD
|
|
Description
|
The ability to close a JIRA post as resolved should only be available to Linden employee or the original poster. Just because some other resident does not like the post, or in their opinion it duplicates another post, or they think it is resolved, should NOT give them the ability to close a post. This ability to close another's post can easily result in abuse and should be removed.
DRD |
Show » |
|
Resolving an issue is sending it back to the reporter for review.
Resolved
This is an implicit assignment back to the reporter of the issue. It is not closed yet, but rather in a state of limbo that depends on the resolution. It's up to the Reporter to decide whether to reopen an issue, or close it.