NFV Issue Tracker: Difference between revisions

From NFVwiki
No edit summary
No edit summary
 
(36 intermediate revisions by 5 users not shown)
Line 1: Line 1:
ETSI's Issue Tracker allows '''anyone''' to report feedback on ETSI NFV public DRAFTs available in the '''[http://docbox.etsi.org/ISG/NFV/Open/Drafts/ NFV Open Area]'''. <small>(this area only contains the ISG NFV drafts which have been made public, i.e. most of them).</small> <br />
== Login to the Issue Tracker ==
There are 2 ways of accessing the Issue Tracker:
'''Login with EOL:''' NFV members and participants can login to the ETSI NFV Issue Tracker with their '''ETSI Online (EOL) account''' (used to log into the ETSI Portal).
# go to the '''[http://forge.etsi.org/mantis/main_page.php?project_id=153 ETSI Issue Tracker]''' home page, then in the top left corner choose the project "NFV Specifications" and then the sub-project corresponding to the draft on which you want to provide feedback.
 
# Click on one of the direct links in the table below
Go to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker] and login.
In both cases your will first have to login, or create yourself an account (see instructions further down)
 
User with '''EOL account''' can view and create issues, but users without EOL account can only view issues.
 
Issue tracker allows normal users to submit new issues and view public issues, but does not allow to process issues.
 
Chairs, Vice-Chairs, and Rapporteurs have a "'''Developer'''" or "'''Maintainer'''" role, which additionally allows viewing private issues and processing issues.
 
[[File:Login bug tracker.png|599x599px]]
 
== View Issues ==
1. Go to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker] and login.
 
2. To view the list of all issues, click "'''Issues'''" under "'''Pinned'''" drop down button.
 
3. To view issues by '''assignee''', '''author''', or '''label''', click the search bar and choose the relevant option.
 
4. To find issues related to a specific '''specification''', '''version''', or '''other details''', use the '''search bar''' to enter your keywords.
 
[[File:Review issues.png|707x707px]]
 
 
5. To view the details of a specific issue, click title of the issue.
 
[[File:To open existing issue.png|707x707px]]
 
=== Else how to navigate to the Issues Repository ===
1. Go to the [https://forge.etsi.org/rep/nfv/ ETSI Forge NFV Group].
 
2. Click on the "'''Issues'''" repository.


{| class="wikitable"
[[File:Navigate to issues repo.png|707x707px]]
! style="font-weight: bold;" | Draft Reference
! style="font-weight: bold;" | view scope & schedule
! style="font-weight: bold;" | Direct link to Issue Tracker
|-
|  EVE001 "Hypervisor Rqmts spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44587 EVE001 details]
|[http://forge.etsi.org/mantis/set_project.php?project_id=153;172&make_default=no&ref=view_all_bug_page.php EVE001 issue tracker]
|-
|  EVE002 "MEF Use Cases report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46018 EVE002 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=173 EVE002 issue tracker]
|-
|  EVE003 "NFVI Node Arch report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44529 EVE003 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=174 EVE003 issue tracker]


|-
3. View issues as mentioned in the [https://nfvprivatewiki.etsi.org/index.php?title=Issue_Tracker_Process#:~:text=2.%20To%20view%20the%20list%20of%20all%20issues%2C%20click%20%22Issues%22%20under%20%22Pinned%22%20drop%20down%20button. Step 2] of the previous section.
|  EVE004 "Virtualisation technologies Report"
|  [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44586 EVE004 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=175 EVE004 issue tracker]
|-
|  EVE005 "SDN usage in NFV Report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44516 EVE005 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=176 EVE005 issue tracker]
|-
|  IFA001 "Acceleration 1 - UCs report"
|[http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45981 IFA001 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=160 IFA001 issue tracker]
|-
|  IFA002 "Acceleration 2 - VNF Intface Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45830 IFA002 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=161 IFA002 issue tracker]
|-
|  IFA003 "Acceleration 3 - vSwitch Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45980 IFA003 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=162 IFA003 issue tracker]
|-
|  IFA004 "Acceleration 4 - Mgmt aspects Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45982 IFA004 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=163 IFA004 issue tracker]
|-
|  IFA005 "Or-Vi ref point Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46011 IFA005 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=157 IFA005 issue tracker]
|-
|  IFA006 "Vi-Vnfm ref point Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46010 IFA006 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=158 IFA006 issue tracker]
|-
|  IFA007 "Or-Vnfm ref point Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46013 IFA007 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=164 IFA007 issue tracker]
|-
|  IFA008 "Ve-Vnfm ref point Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45987 IFA008 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=165 IFA008 issue tracker]
|-
|  IFA009 "MANO architectural options report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45986 IFA009 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=166 IFA009 issue tracker]
|-
|  IFA010 "MANO Functional Rqmts Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45979 IFA010 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=167 IFA010 issue tracker]
|-
|  IFA011 "VNF Packaging Spec"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44577 IFA011 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=168 IFA011 issue tracker]
|-
|  IFA012 "Os-Ma-Nfvo ref point Spec - svc mgmt & info model"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44576 IFA012 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=169 IFA012 issue tracker]
|-
|  IFA013 "Os-Ma-Nfvo ref point Spec - info model"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45988 IFA013 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=170 IFA013 issue tracker]
|-
|  IFA014 "Network Service Templates Specification"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46641 IFA014 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=171 IFA014 issue tracker]
|-
|  REL002 "Scalable Arch for Reliability Report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44582 REL002 details]
| [http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=177 REL002 issue tracker]
|-
|  REL003 "E2E reliability models report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46015 REL003 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=178 REL003 issue tracker]
|-
|  REL004 "Active monitoring & failure detection report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46041 REL004 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=179 REL004 issue tracker]
|-
|  SEC002 "Security features in mgmt sofware report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=43785 SEC002 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=180 SEC002 issue tracker]
|-
|  SEC004 "LI report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44555 SEC004 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=181 SEC004 issue tracker]
|-
|  SEC005 "Certificate mgmt report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44584 SEC005 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=182 SEC005 issue tracker]
|-
|  SEC006 "Sec & Regulation report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46039 SEC006 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=183 SEC006 issue tracker]
|-
|  SEC007 "NFV Attestation report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=44578 SEC007 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=184 SEC007 issue tracker]
|-
|  SEC008 "Security Monitoring report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=45992 SEC008 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=185 SEC008 issue tracker]
|-
|  SEC009 "UCs for multi-layer host admin"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46661 SEC009 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=186 SEC009 issue tracker]
|-
|  TST001 "Pre-deployment Validation report"
| [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46009 TST001 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=187 TST001 issue tracker]
|-
|  TST002 "Iop Testing Methodology report"
|  [http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46043 TST002 details]
|[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=188 TST002 issue tracker]
|}


== Login to the Issue Tracker ==
== Submitting an Issue to the Issue Tracker ==


If you are an ETSI Member or Participant, use your existing '''ETSI OnLine (EOL) account''' (used to log into the ETSI Portal) to login to the ETSI NFV Issue Tracker.
=== For Non-EOL Users ===
Non-EOL users cannot report issues directly via the '''ETSI NFV Issue Tracker'''. However, it is recommended that they submit their issues by sending an email to "'''NFVsupport@etsi.org"'''.


If you have no EOL account, you can report issues as well, yet you have to create yourself an account on the issue tracker (a local account).
=== For EOL Users ===
'''Create local account:''' The ETSI NFV Issue Tracker is also open to the general public: creating a local account only requires a username and a valid e-mail address, which is verified in the process.  
Go to the [https://forge.etsi.org/rep/nfv/issues/-/issues ETSI NFV Issue Tracker] and login.


New accounts have a "'''Reporter'''" role by default, which allows to submit new issues and view public issues.
Before creating a new issue, please check that:


[[File:login_bug_tracker.png.png|800px|Login Bug Tracker]]
a) The issue still exists in the latest version of the respective GS document, and


== Submit a new Issue ==
b) The issue has not yet been reported by someone else. If the latter is the case, please add a comment to the existing issue rather than reporting a new one.
Connect to the '''[http://forge.etsi.org/mantis/view_all_bug_page.php?project_id=153 ETSI Issue Tracker]''' and login.
On the main screen choose project "NFV Specifications" and the sub-project for the corresponding GS document


'''Before submitting a new issue,''' please ensure that your issue has not already been reported by someone else. If it is the case, then the most appropriate manner to add information to the existing issue consist in adding a note, but unless necessary, avoid reporting a new issue.
To create a new issue:
# Go to [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker], click "'''Issues'''" under "'''Pinned'''" drop down button, and click "'''New issue'''".[[File:New issue.png|center|806x806px]]
# The '''Type''' is default set to "'''Issue'''" don't change it.
# '''Issue Title:''' In the issue Title input field, provide a clear and concise one-line summary of the issue.
#* '''Following the format: [Version] <NFV-Specification> <Issue_title>'''
#* '''For example:''' [v5.1.1] NFV-SOL003 Missing attribute in Query Compute Resources
#'''Issue description:''' In the description input box, clearly explain the issue. Describe what the issue is, what the expected outcome should be, and include any additional details or links to relevant documents if available.
#'''Setting additional fields:'''
#*'''Assignee:'''  If you are going to resolve the issue yourself, choose "'''assign yourself'''" in the "'''Assignee'''" field. Otherwise, its Chair, Co-chair, or rapporteur, responsibility to assign the issue to the relevant individual.
#*'''Labels:''' Use labels to help organize and filter issues. When creating an issue, make sure to:
#**Add the appropriate ISG NFV Working Group (WG) label (e.g., "'''NFV-SOL'''" for a SOL specification issue).
#**Choose a label that describes the issue category: '''Bug''', '''Clarification''', or '''Feature Gap'''.
#*'''Dates and Milestone:''' If you are unsure with the dates and milestone, leave these fields as they are. These fields are supposed to be managed by Chairs, Vice-Chairs, or Rapporteurs, if needed.
#Once all necessary details are added, click "'''Create issue'''" to submit.
[[File:How to add new issue.png|center|796x796px]]
'''In case of confidential issues:'''


'''To submit a new issue:'''
* If this is an ETSI NFV internal issue (e.g. gap tracking by the rapporteur) and this issue is still confidential because it refers to a non-public document, send it via email to "'''NFVsupport@etsi.org'''".
# In the appropriate sub-project click "Report Issue".<br />[[File:Create_Report.png|800px]]<br /><br />
* Note: We should keep our own issues public whenever possible, as this helps reducing duplicate reports.
# In the form, choose the most appropriate category for the new issue (see table below):<br />[[File:Create_Report_Form.png|800px]]<br /><br />
# Select the latest version of the GS document that contains the issue.
# Provide a descriptive one-line summary of the issue.
# Provide a detailed description of the issue: What specific issue did you encounter and where? What would you have expected to find instead?
# Optionally, provide additional information. This is the field to put references to external documents, if any.
# Keep the "View Status" as "public"
# Click "Submit Report".


Issue categories:
Issue categories:
Line 168: Line 76:
! Semantic
! Semantic
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| '''Bug'''
| Bug
| Some aspect of the spec cannot be implemented as described.
| Some aspect of the spec cannot be implemented as described.
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| '''Clarification'''
| Clarification
| Some aspect of the spec is ambiguous or unclear.
| Some aspect of the spec is ambiguous or unclear.
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| '''Feature Gap'''
| Feature Gap
| The specs are missing a feature (e.g. an operation, parameter) without which the described features cannot be implemented.
| The specs are missing a feature (e.g. an operation, parameter) without which the described features cannot be implemented.
|}
|}
== Monitoring Relevant Issue(s) ==
By default, the issue reporter (or creator) receives email notifications when someone comments on the issue, updates its status (e.g., closed or reopened), or performs other related actions. However, if you want to manage notifications for the issue(s) you are involved in:
1. Log in to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker].
2. In the Issue repository, click the '''bell icon''' in the issue repository and select "'''Participate'''" to receive updates on issues you are part of.
3. Select "'''On mention'''" option, to get notified only when you are specifically mentioned in a comment.
4. To stop receiving email notifications, select the "'''Disabled'''" option.
[[File:Relevant notification settings.png|762x762px]]
== Monitor All Issues ==
Users can also subscribe to receive email notifications for all activities within the repository.
1. Log in to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker].
2. In the Issue repository, click the '''bell icon''' in the issue repository and select "'''Watch'''" to get notified for all activity in the Issue repository.
3. To stop receiving email notifications, select the "'''Disabled'''" option.
[[File:All notification settings.png|762x762px]]

Latest revision as of 13:53, 25 July 2025

Login to the Issue Tracker

Login with EOL: NFV members and participants can login to the ETSI NFV Issue Tracker with their ETSI Online (EOL) account (used to log into the ETSI Portal).

Go to the ETSI NFV Issue Tracker and login.

User with EOL account can view and create issues, but users without EOL account can only view issues.

Issue tracker allows normal users to submit new issues and view public issues, but does not allow to process issues.

Chairs, Vice-Chairs, and Rapporteurs have a "Developer" or "Maintainer" role, which additionally allows viewing private issues and processing issues.

Login bug tracker.png

View Issues

1. Go to the ETSI NFV Issue Tracker and login.

2. To view the list of all issues, click "Issues" under "Pinned" drop down button.

3. To view issues by assignee, author, or label, click the search bar and choose the relevant option.

4. To find issues related to a specific specification, version, or other details, use the search bar to enter your keywords.

Review issues.png


5. To view the details of a specific issue, click title of the issue.

To open existing issue.png

Else how to navigate to the Issues Repository

1. Go to the ETSI Forge NFV Group.

2. Click on the "Issues" repository.

Navigate to issues repo.png

3. View issues as mentioned in the Step 2 of the previous section.

Submitting an Issue to the Issue Tracker

For Non-EOL Users

Non-EOL users cannot report issues directly via the ETSI NFV Issue Tracker. However, it is recommended that they submit their issues by sending an email to "NFVsupport@etsi.org".

For EOL Users

Go to the ETSI NFV Issue Tracker and login.

Before creating a new issue, please check that:

a) The issue still exists in the latest version of the respective GS document, and

b) The issue has not yet been reported by someone else. If the latter is the case, please add a comment to the existing issue rather than reporting a new one.

To create a new issue:

  1. Go to ETSI NFV Issue Tracker, click "Issues" under "Pinned" drop down button, and click "New issue".
    New issue.png
  2. The Type is default set to "Issue" don't change it.
  3. Issue Title: In the issue Title input field, provide a clear and concise one-line summary of the issue.
    • Following the format: [Version] <NFV-Specification> <Issue_title>
    • For example: [v5.1.1] NFV-SOL003 Missing attribute in Query Compute Resources
  4. Issue description: In the description input box, clearly explain the issue. Describe what the issue is, what the expected outcome should be, and include any additional details or links to relevant documents if available.
  5. Setting additional fields:
    • Assignee: If you are going to resolve the issue yourself, choose "assign yourself" in the "Assignee" field. Otherwise, its Chair, Co-chair, or rapporteur, responsibility to assign the issue to the relevant individual.
    • Labels: Use labels to help organize and filter issues. When creating an issue, make sure to:
      • Add the appropriate ISG NFV Working Group (WG) label (e.g., "NFV-SOL" for a SOL specification issue).
      • Choose a label that describes the issue category: Bug, Clarification, or Feature Gap.
    • Dates and Milestone: If you are unsure with the dates and milestone, leave these fields as they are. These fields are supposed to be managed by Chairs, Vice-Chairs, or Rapporteurs, if needed.
  6. Once all necessary details are added, click "Create issue" to submit.
How to add new issue.png

In case of confidential issues:

  • If this is an ETSI NFV internal issue (e.g. gap tracking by the rapporteur) and this issue is still confidential because it refers to a non-public document, send it via email to "NFVsupport@etsi.org".
  • Note: We should keep our own issues public whenever possible, as this helps reducing duplicate reports.

Issue categories:

Category Semantic
Bug Some aspect of the spec cannot be implemented as described.
Clarification Some aspect of the spec is ambiguous or unclear.
Feature Gap The specs are missing a feature (e.g. an operation, parameter) without which the described features cannot be implemented.

Monitoring Relevant Issue(s)

By default, the issue reporter (or creator) receives email notifications when someone comments on the issue, updates its status (e.g., closed or reopened), or performs other related actions. However, if you want to manage notifications for the issue(s) you are involved in:

1. Log in to the ETSI NFV Issue Tracker.

2. In the Issue repository, click the bell icon in the issue repository and select "Participate" to receive updates on issues you are part of.

3. Select "On mention" option, to get notified only when you are specifically mentioned in a comment.

4. To stop receiving email notifications, select the "Disabled" option.

Relevant notification settings.png

Monitor All Issues

Users can also subscribe to receive email notifications for all activities within the repository.

1. Log in to the ETSI NFV Issue Tracker.

2. In the Issue repository, click the bell icon in the issue repository and select "Watch" to get notified for all activity in the Issue repository.

3. To stop receiving email notifications, select the "Disabled" option.

All notification settings.png

Retrieved from "https://nfvwiki.etsi.org/index.php?title=NFV_Issue_Tracker&oldid=3895"