Viewing issues in Jira

energyinterop message

Subject: Viewing issues in Jira

From: William Cox <wtcox@coxsoftwarearchitects.com>

To: EITC <energyinterop@lists.oasis-open.org>

Date: Thu, 13 Jan 2022 10:51:55 -0500

Viewing the open and active issues in Jira can be done with the view all items.

does it for me. I added the "Label" column and hid Reporter using the "Columns" menu on the right hand side.

This lets you see all issues, sort (click the column header) in various ways, and see the broader picture.

Thanks!

bill

On 1/13/22 10:46 AM, William Cox wrote:

Apologies - I forgot to manually turn off notifications for each change; I filter my Jira notifications so I don't see them in my main EITC folders. Since we'll be working with the issues in Jira, I strongly recommend that you do the same.

The subject string to use for filtering (email to energyinterop@lists.oasis-open.org) is

[energyinterop] [OASIS Issue Tracker]

The "dont send notifications" was disabled for a while, and I didn't think of it.

Update: I don't see that option on changes to individual issues, only on bulk changes.

The next flock will be to resolve the editorial issues after the meeting today, and set status and state.

bill

On 1/13/22 10:34 AM, wtcox coxsoftwarearchitects.com wrote:

Here's the updated list of labels after classifying all comments in Jira. These have been applied; a few items have two labels.

"editorial" is a standard Jira built-in label. New labels are in ALL CAPS.

   •   editorial comments related to editorial and explanatory material including clarifications. Clarification of whatâs intended. Key words include facet service
   •   PREREQ including comments on _expression_ of units, mantissa and granularity for quantities and prices, and Standard Terms (comments related to non-hour-aligned markets, etc.)
   •   RES-PROD-INSTR for resource-product-instrument comments. Notes on how EMIX is clustered and factored differently to enable more dynamic market discovery and interaction.
   •   ARCH-CONF labels both architectural issues and conformance to base standards and to CTS. Include clarified discussion on refactoring and applicability to base standards (similar to e.g. IEC 62746-10-3 mappings)
   •   FACET including facet description, definition, and clarification/refinement. For Facet structure, see ARCH-CONF. For example, clarify the Position facet, and address comments on Tender and Transaction and other facets
   •   MARKET definitions, assumptions, capabilities, integration, Market Information facet comments
   •   OTHER

Remember that TC members may add comments directly in Jira as well - use your workspace login at

    https://issues.oasis-open.org/projects/ENERGYINTEROP/issues/ENERGYINTEROP-727?filter=allopenissues

Thanks!

bill

--

William Cox

Email: wtcox@CoxSoftwareArchitects.com

Web: http://www.CoxSoftwareArchitects.com

+1 862 485 3696 mobile

William Cox

Email: wtcox@CoxSoftwareArchitects.com

Web: http://www.CoxSoftwareArchitects.com

+1 862 485 3696 mobile