Difference between revisions of "Open Development User Group"
Jump to navigation
Jump to search
(invisible jira issues) |
m (current key of STORM-864) |
||
| Line 19: | Line 19: | ||
--> | --> | ||
# Can {{jira|STORM-864}} be made publicly visible again, please? ([[User:Boroondas Gupte|Boroondas Gupte]]) | # Can {{jira|STORM-864}} (now {{jira|SH-1426}}) be made publicly visible again, please? ([[User:Boroondas Gupte|Boroondas Gupte]]) | ||
#* It seems that a lot of those issues which are moved to generally non-public jira projects (with some issues made manually visible) become invisible to the public by accident. Could jira be set up so that when a publicly visible issue is moved to a non-public project, | #* It seems that a lot of those issues which are moved to generally non-public jira projects (with some issues made manually visible) become invisible to the public by accident. Could jira be set up so that when a publicly visible issue is moved to a non-public project, | ||
#** the issue stays visible by default, unless the mover explicitly makes it invisible (i.e. default visibility for moved objects would be the issue's old visibility, '''not''' the default visibility for new issues in the destination project)<br />''or'' | #** the issue stays visible by default, unless the mover explicitly makes it invisible (i.e. default visibility for moved objects would be the issue's old visibility, '''not''' the default visibility for new issues in the destination project)<br />''or'' | ||
Revision as of 07:36, 12 June 2011
Open Source Policies, Resources for Open Contributions, and progressing contributions through the Snowstorm process.
Chaired by Oz Linden of the Snowstorm Team.
Agenda
The agenda for the next meeting is:
- Can STORM-864 (now SH-1426) be made publicly visible again, please? (Boroondas Gupte)
- It seems that a lot of those issues which are moved to generally non-public jira projects (with some issues made manually visible) become invisible to the public by accident. Could jira be set up so that when a publicly visible issue is moved to a non-public project,
- the issue stays visible by default, unless the mover explicitly makes it invisible (i.e. default visibility for moved objects would be the issue's old visibility, not the default visibility for new issues in the destination project)
or - the mover has to explicitly choose whether the issue will become invisible or stay visible (i.e. no default). (It should not possible to complete the move without explicitly making the decision.)
- the issue stays visible by default, unless the mover explicitly makes it invisible (i.e. default visibility for moved objects would be the issue's old visibility, not the default visibility for new issues in the destination project)
- Please ask the different Linden Teams with own jira projects to regularly re-evaluate whether the default (in)visibility for issues in those projects should remain as-is.
- It seems that a lot of those issues which are moved to generally non-public jira projects (with some issues made manually visible) become invisible to the public by accident. Could jira be set up so that when a publicly visible issue is moved to a non-public project,
- OPEN Issue Triage (Oz Linden)
Archive
Records of past meetings: Open Development User Group/Archive
- See the list of other user groups.