This guide aims to introduce Beam contributors to the basics of using the Apache Jira for Beam development.

First Steps

...

How to get started on Jira

To start collaboration in the Apache Beam Jira:

1. Access the Apache Jira dashboard.

2. Read the introduction to see what permissions are available to users

...

1. and to create an account.

...

1.  
   

   Note
   Only developers on a project have full permissions for modifying issues.

   
   

2. To get this permission

...

1. :
   1. Email the dev@ mailing list

...

1. 2. Introduce yourself 
   3. Ask to be added as a contributor in the Beam issue tracker, including your ASF Jira Username. For example this welcome email.

...

How to navigate Jira

The Apache Jira is used for many Apache projects, not just Beam. The Projects menu on To navigate in the Beam specific issues:

1. Go to https://issues.apache.org/jira
2. On the top bar

...

1. , select the Projects > View All Projects to browse and see what project you are currently browsing.

...

2. Search for "Beam" and select Beam.

...

...

Searches and Filters

When searching for issues the default search page includes all issues and projects. To narrow this search down, select from filters near the top of the search. This allows you to narrow the search down to only Beam issues, among other criteria. Commonly used filters for Beam include Project, Status, Component, and Label. Some of these filters may not be visible by default in the basic Basic view. To use them, select the dropdown menu titled More, and then select view all issues or create a search:

1. Select View all issues and filters.
2. Select the More dropdown menu.
3. Select the criteria you are looking for, and

...

1. you can use it in the list of criteria you can use to filter.

...

1. Select Save as to save a commonly used filter.

Saved filters can be viewed by hovering on the left side of the page to reveal the filters menu.

Creating Issues

This guide will not cover every field that you can be used use when creating an issue. Instead, but it will instead clarify any commonly-used fields that may be unintuitive for a first-time user , as well as cover and include any Beam-specific details.

Image Added

Issue Type field 

This field lists what type of issue is being createdyou are creating. The most import important are "Bug" if :

• Bug. If you found a bug

...

• that needs to be fixed.
• New Feature

...

• . If you are recording a feature request which has yet to be developed.

Click theImage Added icon to view the . Use the question mark button next to the drop-down to view the list of descriptions for all issue types. There are no particular rules about when to use other types. If you are unsure, stick to Bug or New Feature. Someone from the Beam community will check the details anyhow.

Priority field

This field lists the priority of the issue being created. Like with issue type, use the question mark button next to the drop-down to view the list of descriptions for all priorities.Priority is vague, you are creating. The Priority is vague and can mean different things depending on issue typethe Issue Type. Beam uses 5 five levels of severity; they may correspond to "P0" through "P4" in other systems. You can think Think of them like this:

• P0 Blocker
: get
• . Get paged, stop whatever you planned on doing, work late to fix it.
• P1 Critical
: continually
• . Continually update everyone on the status and shouldn't sit around unassigned.
• P2 Major
: most
• . Most things here
; they
• are
important
• necessary but not an interrupt - if unsure, use Major, and someone from the community will review the details.
• P3 Minor
: nice
• . Nice-to-have things
,
• may not make it onto regular planning and
roadmapping
• road mapping but still useful if someone wants to do it.
• P4 Trivial: a
special
• particular category for typos or minor cleanups that might be good for newcomers just to get started with the project
,
• or build system
, etc

Components

• .

Click theImage Added icon to view the descriptions for all issue types.

Component/s

You can find a A list of all Beam components and their descriptions on the

Components page of can be found in the components page for the project. These components correspond to different areas within the Beam project, and you should file all issues should be filed in one or more relevant components. For this reason, contributors should review the components page and have a basic familiarity with the components of the project.

Labels

A label is an arbitrary text string attached to an issue. Labels are used to tag issues for searches , and are usually used to identify aspects of an issue that are not directly related to code. Beam has and uses a few labels that are used systematically:

• starter
-
• .  This label means that it is
a good
• an excellent task to get started contributing to Beam.

• triaged

-

• . This label means that an experienced member of the community has reviewed the component, priority, and issue type

,

• ; and that someone who understands the issue has been contacted.  

  Note
  Do not add this label to new issues or no one will look at it.

  
  

• sickbay
-
• . This label means that the Jira is about a test that was disabled because it was broken, and it should be fixed and re-enabled.
• flake
-
• . This label means the Jira is about a flaky test
that is flaky
• , so it harms everyone's productivity
, a
• . A non-
sickbayed
• sickbay flake must always be a Critical priority or higher.

Contributors are encouraged to label issues in whatever other ways they want. However, there are no expectations or requirements regarding labels, so don't expect too much consistency should not be expected.