Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAA-1669: Jira flow - new page. [master] #1441

Merged
merged 12 commits into from
Jan 30, 2017

Conversation

hunch7
Copy link
Contributor

@hunch7 hunch7 commented Jan 20, 2017

No description provided.


## When to create issues

To decide whether you should create a Jira issue, use [Kaa Stack Overflow](http://stackoverflow.com/questions/tagged/kaa) to consult with Kaa team and find out whether your issue:
Copy link
Contributor

@rasendubi rasendubi Jan 20, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, that's not what Stack Overflow is for. Users are expected to create Jira issues whenever they believe they have found a bug or have a feature request. Though, they should search the Jira to find out if the issue already exists first.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

| Description | Provide a meaningful description of the issue with all the details you find relevant. Describe the steps to reproduce the issue, and the environment in which you found it. In general, feel free to share any information you think is related to the issue. See also [Issue types](#issue-types) for specific information to be provided depending on the issue type. |
| Attachment | Feel free to attach images, documents and other files you think can help understand the issue-related information. |

>**NOTES:** Please do not fill any other fields, they will be managed by the Kaa team members.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not forbid that on permission level?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Will talk to Jira admin.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed with Jira admin, these permissions will be configured after we migrate to Jira 7 which is planned to be done at the end of the current sprint.

## Working on issues

After you submitted an issue, it will appear in the selected project space for the Kaa team members to spot.
The work on the issue can begin after the team lead included it in a sprint and a person is assigned to the issue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section ignores the fact that any user can work on the issue (not team members only)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@@ -18,15 +18,15 @@ We would love to see you mastering the Kaa source code; however, writing code is
Feel free to use all of the contribution options:

- Join [Kaa Stack Overflow](http://stackoverflow.com/questions/tagged/kaa) to find answers to common user questions, ask your own Kaa-related questions, and help others in the community.
- Use [Jira](http://jira.kaaproject.org/browse/KAA/) to provide feedback, make features and functionality suggestions, and help other community members.
- Use [Jira](http://jira.kaaproject.org/) to provide feedback, make features and functionality suggestions, and help other community members.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a link to Jira flow here, too. (As it is not limited to contributing to the source code.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

You may want to send some Kaa error logs to help resolve an issue.
To do this:

1. [Change the log level for the Kaa service to “TRACE”]({{root_url}}Administration-guide/Troubleshooting/#how-to-change-the-service-logging-level).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't redirect to the specific section of the documentation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.


1. [Change the log level for the Kaa service to “TRACE”]({{root_url}}Administration-guide/Troubleshooting/#how-to-change-the-service-logging-level).

2. [Clear the Kaa logs]({{root_url}}Administration-guide/Troubleshooting/#how-to-clear-the-kaa-logs).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the same

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.


3. Reproduce your issue.

4. [Download the Kaa logs from the Sandbox]({{root_url}}Administration-guide/Troubleshooting/#how-to-download-the-kaa-logs-from-the-sandbox).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the same

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@vadimol vadimol merged commit beaa3c0 into kaaproject:master Jan 30, 2017
@hunch7 hunch7 deleted the kaa-1669-jiraFlow-master branch January 31, 2017 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants