2019-03-31: CONTRIB and LIAISE attachment handling and naming has been updated

SANDBOX behaves exactly the same as CONTRIB, so you can create SANDBOX issues to experiment with the new mechanism.

These are the main changes (various bugs have also been fixed). Most of the changes are intended to make attachment handling easier and less error-prone, but there are also some new features. See the Jira Contribution Attachments wiki page for full details, including examples and FAQ. Please email tools@broadband-forum.org if you have any problems or questions.

#ChangeDescription
1Multiple files with same versionIt was already possible to have multiple files with the same version and different extensions (e.g. file-00.docx and file-00.pdf) but this has now been extended to allow multiple files with the same version and different titles (e.g. file-clean-00.docx and file-changes-00.docx)
2Example filenamesThe "Attach Files" screen shows some example filenames (based on the current attachments) that illustrate what the actual filenames will look like. The example filenames are updated whenever the "Title" field is updated (or the "Company" field, if it's visible). To trigger the update, click outside the box
3Company name overrideBBF Technical Committee leaders (i.e. members of the tcleaders group) can override the "company" part of the actual filename; this is intended only for when a leader (as part of their BBF leadership role) uploads files on behalf of another user, WA or PS
4Liaison attachments

You now use the "Attach Files" screen to upload LIAISE attachments. This is simpler than for CONTRIB: the actual filename will be same as the uploaded filename, except that:

  • The appropriate LIAISE-nnn prefix will be added if not already present (it's an error if the filename already has the wrong prefix)
  • For outgoing liaisons, a version number will be added if not already present

2019-03-12: 2019Q1 ZIP files are available for download

The Q1 2019 Contributions page has a ZIP file for each Work Area (and a ZIP file for liaisons). Each ZIP file contains an HTML index page and the Work Area's contributions.

2018-12-04: 2018Q4 ZIP files are available for download

The Q4 2018 Contributions page has a ZIP file for each Work Area (unless the WA has no contributions). Each ZIP file contains an HTML index page and the Work Area's contributions.

2018-11-18: CONTRIB attachment handling and naming has changed

SANDBOX behaves exactly the same, so you can create SANDBOX issues to experiment with the new mechanism.


The company name is no longer included in "Draft" filenames, e.g. (assuming that the title field is empty ) if I upload WT-123_Rev-02.docx then the actual attachment filename will be the same, whereas previously it would have been WT-123_bbf_Rev-02.docx.

To attach files, first create the issue, then click the "Attach Files" button and follow the instructions. See the Jira Contribution Attachments wiki page for full details, including examples and FAQ. Please email tools@broadband-forum.org if you have any problems or questions.

2018-11-13: New quick search for BBF projects

You may have noticed that it doesn't work to type a term like "WT-101" into the quick search box. This is because Jira thinks that this is an issue key (project="WT", number=101).

However, now you can use quick search to search for BBF projects. Simply omit the hyphen! For example, search for "WT101" (or "wt101"... case doesn't matter). You can omit leading zeros and so could search for "WT69" to find WT-069.

Be aware that this is a string search. It should find all issues with the corresponding "BBF Project" value, but it will also find any issues that happen to contain the search string in a string-valued field, e.g. the issue summary, description or comments.

From anywhere in Jira, enter your search term in the search box near the top right-hand corner of the screen.

Hit enter and immediately see your search results.

Most of the results in this example have "BBF Project" = "WT-069: CPE WAN Management Protocol" but there can be false positives. You can now refine the search if you like.

2018-11-01: Reminder to use "BBF Updated" in filters and subscriptions

The "Updated" field changes whenever any issue attribute changes, even if a wiki page links to an issue. And today it's changed for pretty much every issue created in the last three years (as a result of setting the "BBF Company" field).

So you will almost always want to use the "BBF Updated" field in filters and subscriptions! The "Updated" field will give you far too many false positives.

2018-11-01: New "BBF Company" field


This field is available in all Jira projects, not just in CONTRIB. If you don't see it, this might be because you're using one of the OB (Open Broadband) projects... if this happens, please create a JIRA TOOLS issue or email tools@broadband-forum.org.

A new "BBF Company" field has been added. It's set on issue creation and can only subsequently be changed by an administrator. The field value will not change if the creator of the contribution moves to a new company.

This field has been set on existing issues created since January 2016. Its value is based on the current affiliation of the creator (reporter) and so may be wrong in a few cases. If you find any wrong values, please email tools@broadband-forum.org.

The field values are options selected from a list (like "BBF Project" etc.). This means that they're easy to change (let us know!). There are three special "company names": "Individual" (for individual members), "Distinguished Fellow" (for fellows) and "Unknown" (if the creator's username doesn't match a known BBF member company email domain).

Of course, you can use this field to search for contributions. It's better than the "Reporter Domain" field because it handles cases where a company has multiple email domains (and because, as already noted, it's only set on issue creation).

Here's how to find all CONTRIB issues created by BBF staff.

This is a case where the JQL (Jira Query Language) might actually be easier to understand than a picture!

project = CONTRIB AND "BBF Company" = "Broadband Forum" ORDER BY created DESC




2018-11-01: "BBF Project", "BBF Project Stream" and "BBF Work Area" extensions

The "BBF Project", "BBF Project Stream" and "BBF Work Area" fields have always been used in the CONTRIB Jira project but are now available in other Jira projects. This means that you can use these fields to search for relevant contributions anywhere, not just in CONTRIB.

For example, the Common YANG Work Area's WT-383: Common YANG Modules for Access Networks project has contributions in CONTRIB and in its YMCMN Jira project. Previously you could only use "BBF Project" to search for its contributions in CONTRIB but now all YMCMN issues have "BBF Project" = "WT-383: Common YANG Modules for Access Networks".

Here's how to find all WT-383 contributions across all Jira projects (note "Project: All"!). The results are a mixture of CONTRIB and YMCMN issues.

This is a case where the JQL (Jira Query Language) might actually be easier to understand than a picture!

"BBF Project" = "WT-383: Common YANG Modules for Access Networks" ORDER BY created DESC


2018-10-09: Jira 7.12.1: new look and feel, search improvements etc.

Jira has been upgraded from 7.6.2 to 7.12.1. You might notice a few changes:

2018-09-04: New "BBF Updated" field

This field is available in all Jira projects, not just in CONTRIB. If you don't see it, this might be because you're using one of the OB (Open Broadband) projects... if this happens, please create a JIRA TOOLS issue or email tools@broadband-forum.org.

A new "BBF Updated" field has been added. It indicates the last time that a comment was added (or edited) or a file was attached to the issue. In other words, it indicates when the issue was last "really" changed, and will not change just because a label was added, someone was assigned, the priority was changed etc.


This (fake) contribution was created at 04/Sep/17 3:06 PM and a file was attached at the same time. It was subsequently resolved at 20/Aug/18 11:51 AM and this is its "Updated" time. However, its "BBF Updated" time is 04/Sep/17 3:06 PM because this is when the last comment or file was added.


This shows how to search for CONTRIB issues with "BBF Updated" values in the last week.


2018-06-06: 2018Q2 ZIP files are available for download

The Q2 2018 Contributions page has a ZIP file for each Work Area (unless the WA has no contributions). Each ZIP file contains an HTML index page and the Work Area's contributions.

2018-06-04: CONTRIB email subjects indicate project and work area [UPDATE]

The email subject used to include information about what happened, e.g. (updated CONTRIB-18088) rather than (CONTRIB-18088), but we realised that this made email filters harder to create, so this extra information is no longer included.


CONTRIB email subjects indicate the project and work area(s), which should make it easier to filter out emails of interest. For example:

BBF-JIRA {WT-114} [PHYtx] (CONTRIB-18088) Issues List for WT-114i3a3


FieldExplanation
BBF-JIRAThe subject always begins with this. Including BBF- allows you to easily distinguish BBF JIRA emails and your own company JIRA emails
{WT-114}The project's short name is enclosed in curly braces. If the project is Not Assigned, this is shown as {NA}
[PHYtx]The work area short name is enclosed in square brackets. If the work area is Not Assigned, this is shown as [NA], and if there are multiple work areas they are all shown, each with its own set of square brackets
(CONTRIB-18088)

The CONTRIB number is enclosed in round brackets


Issues List for WT-114i3a3
The contribution summary (title)


Also:

  • When a contribution is created, the email body includes additional BBF-specific information.


  • Additional info is also shown in LIAISE email subjects and bodies

    In the subject, the first field (in the curly braces) is the partner organization.

    BBF-JIRA {IEEE 1914} [R&T] (LIAISE-105) iLS from IEEE 1914 -- P1914.3 Radio over Ethernet (RoE)


2018-04-05: new contributions can't set "BBF Work Area" to "Not Assigned"

The problem with setting "BBF Work Area" to "Not Assigned" is that no-one knows which WA should handle the contribution, and it can fall through the gaps. Therefore, when creating a new contribution you must now always select a WA.

2018-03-21: 2018Q1 ZIP files are available for download

The Q1 2018 Contributions page has a ZIP file for each Work Area. Each ZIP file contains an HTML index page and the Work Area's contributions.

2018-03-17: bbf-2018q1-agenda label has been added to all 2018Q1 contributions

bbf-2018q1-agenda label has been added to all Q1 contributions. It was defined in a similar way to the  bbf-2017q4-agenda label (but using the date range appropriate for the Q1 meeting of course).

Creation of this label caused problems for some Work Area Directors, because the act of creating the label changed contributions' updated field to be slightly after the contribution deadline and this caused searches based on the contribution deadline to regard contributions with the label as being late contributions!

For future meetings we will not be defining such labels, and will provide alternative ways of finding the contributions that should be included in meeting agenda.

2017-11-29: bbf-2017q4-agenda label has been added to all 2017Q4 contributions

bbf-2017q4-agenda label has been added to all Q4 contributions. More specifically, this label has been added to all open (unresolved) contributions that were created or updated between 15th September (the Friday immediately after the Q3 meeting) and the Q4 contribution deadline.

To create this label, the following search was executed shortly after the Q4 contribution deadline, and then the label was added to the matching contributions.

Nothing prevents this label from being added to or removed from additional contributions. Anyone can do this, but please don't abuse your power, and note that all changes are logged!

You can easily define additional searches based on this label. For example, Q4 BUS contributions.

And of course you can save and share these searches. The Q4 2017 Contributions page includes some further examples.

2017-11-29: CONTRIB project stream and work area are selected automatically

When you create a CONTRIB issue, selecting the project will automatically select the project stream and work area. You can then select additional (or different) project streams and/or work areas if you like.

2017-11-29: CONTRIB email subjects indicate project and work area

CONTRIB email subjects indicate the project and work area(s), which should make it easier to filter out emails of interest. For example:

BBF-JIRA {WT-114} [PHYtx] (CONTRIB-18088) Issues List for WT-114i3a3


FieldExplanation
BBF-JIRAThe subject always begins with this. Including BBF- allows you to easily distinguish BBF JIRA emails and your own company JIRA emails
{WT-114}The project's short name is enclosed in curly braces. If the project is Not Assigned, this is shown as {NA}
[PHYtx]The work area short name is enclosed in square brackets. If the work area is Not Assigned, this is shown as [NA], and if there are multiple work areas they are all shown, each with its own set of square brackets
(CONTRIB-18088)

The CONTRIB number is enclosed in round brackets

Currently information about what happened is also included, e.g. (updated CONTRIB-18088), but we will be removing this because we've realised that it causes several problems


Issues List for WT-114i3a3
The contribution summary (title)


Also:

  • When a contribution is created, the email body includes additional BBF-specific information.


  • Additional info is also shown in LIAISE email subjects and bodies

    In the subject, the first field (in the curly braces) is the partner organization.

    BBF-JIRA {IEEE 1914} [R&T] (LIAISE-105) iLS from IEEE 1914 -- P1914.3 Radio over Ethernet (RoE)


2017-11-29: All ARO contributions are now in CONTRIB

The ARO contribution site was made read-only after the Q3 Helsinki meeting, and now all past ARO contributions have been added to the JIRA CONTRIB project, joining CONTRIB-20001, CONTRIB-20002 etc. that were created directly in JIRA.

We've assigned CONTRIB-nnnnn keys by order of creation date:

YearAROCONTRIB
1997dsl1997.001 through dsl1997.247CONTRIB-1 through CONTRIB-247
1998dsl1998.001 through dsl1998.258CONTRIB-248 through CONTRIB-505
...

2016bbf2016.001 through bbf2016.1288CONTRIB-16889 through CONTRIB-18176
2017 Q1-Q3bbf2017.001 through bbf2016.719CONTRIB-18177 through CONTRIB-18895
2017 Q3-Q4
CONTRIB-20001 and counting

All ARO contributions have an External issue ID field whose value is the ARO contribution name (omitting the revision number), e.g. "dsl1997.001". You can easily find an ARO contribution by typing the ARO contribution name in the Search field near the top right-hand corner of the JIRA window. This will find any JIRA issue that contains this string, so the results should always include the contribution that you're looking for, but might also include a few other issues. Of course, you can also search specifically for External issue ID values or patterns.

Suppose you want to search for ARO contribution dsl2003.304.

Quick Search

Type dsl2003.304 into the Search box and hit Enter. That was easy!

Basic Search

Use the More menu to add the External issue ID field, then type dsl2003.304 and hit Enter. That was almost as easy!