User Tools

Site Tools


start

Welcome to the JIRA Project Wiki

Project Status

Glossary of terms

Definitions

Issue Creation

There are 3 ways to create an issue

  1. Public form
  2. Email to issues@omg.org (discouraged because of IP agreement)
  3. Local form of the TF (internal members)

Public Issue Submission

Issue submitted by the general public have the following characteristics:

  • They are normally oriented to a specification or document, not a TF
  • They may not be a real issue, they can be spam or other types of messages
  • There may not be a stablished TF to handle the issue
  • Issues created via email fall into this category

For this reason, the public issue submission procedure has some validations before being directed to a TF for evaluation.

Issues submitted via the Public form wil have a validation step performed by OMG Staff where they will decide the resolution of the issue:

  • Discard the issue with or without comment
  • Send to a Task Force
  • Move to unfiled (because they are valid but there is no TF to handle them)

- Public fields

  • Specification Name and Version
  • OMG Document Number
  • Document Date
  • Chapter / Section
  • Page Number

We assume that issues that reach a task force are filtered for spam messages. Consequently, every issue must follow the entire process. Untriaged issues can be filtered and discarded by OMG staff prior to reaching a task force.

Roles

  • Chairs
  • Voting Members
  • Members
  • Staff

Permissions

  • Anyone can view issues, even public.
  • TF Members (all members) can create issues. [Optional: Since any OMG member can create an issue through the public form, why not allow them to post directly]
  • TF Members are assignable users (can work on issues)
  • TF Members can create proposals
  • TF Members can edit issues
  • Anyone can create comments
  • Chairs can create ballots and set dates
  • Chairs can schedule Issues
  • Only Chairs and voting members can vote on ballots
  • OMG Staff can create Task Forces based on TC decisions
  • OMG Staff can close Task Forces (accept the FTF Report)
  • Pending Who can see the TF Report | Ballot Report/Summary | Issue Votes Summary/Detail

Members Submission Form

This form can be used by existing members and can submit an issue to an existing TF directly. This method does not require a OMG Staff validation since we trust members to submit issues appropietly.

Unassigned Issues

Issued created via email sent to issues@omg.org are not validated as real issues. At this point OMG Staff should review them and they can take the following actions:

  • Discard the issue with or without comment
  • Send to a Task Force
  • Move to unfiled (because they are valid but there is no TF to handle them)

Issue Proposals

While the issue is open or in progress, new proposals can be created. Only one proposal for each type of resolution is allowed.

When the issue is ready to be voted, the chairs will execute the “schedule” action, that will put the issue in an unreleased version, and prevent the editing of the issue or the proposals.

The “new proposal” action:

  • Unordered List ItemConditions: any member can create proposals
  • Validations: only one active proposal per resolution.

The “schedule” action requires at least one proposal to be created previously.

  • Conditions: only chairs can schedule issues
  • Validation: only unreleased versions

Ballots

If a proposal is open for voting does not have votes, it can be reopened. If If a proposal is approved, the issue automatically transitions to approved by TF.

If a proposal does not reach quorum it is rejected, not reopen.

User-Available Fields

  • Due Date
  • Labels
  • Components
  • Assignee
  • Environment

Fields Not Used

  • Worklog

Questions

  • can you close an issue without voting? spam? - we assume that since issues get here after a triage, they should all be voted

Issue Collector

JIRA Information

jira is the jira specific details.

start.txt · Last modified: 2014/05/04 15:06 by admin