nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Netiquette for Jira and Confluence users

Rumceisz

Hi All,

this question is a bit unconventional:)

I start to write a netiquette document for my Jira and Confluence users. Have you got a similar doc at your workplace, environment?

I would like to ask for a help reading such a document. Just for getting started.

Thanks in advance!

Rumi

Accepted answers

RIsk

I always liked this: http://www.businessweek.com/technology/ceo_tipsheet/2007_3.htm

All comments

Ole Kristensen

Welcome to the Grundfos Wiki

Create, Edit and Share all business relevant knowledge with your colleagues.
Please feel free to edit all articles where you are certain that you can add value!
Or at least make a comment below articles.

Everything in the Grundfos Wiki Must be in english
Confidential content should not be applied to the Grundfos Wiki!
Please do not upload files except pictures, diagrams, charts etc.

Apply for your own space for your team, project, department or company by sending a request to Service Desk stating the Title, Purpose of your Wiki space and the person to own the space.

Rumceisz

Hi Ole,

many thanks for sharing your netiquette. Do have same for Jira too?

Regards,
Rumi

RIsk

I always liked this: http://www.businessweek.com/technology/ceo_tipsheet/2007_3.htm

Rumceisz

Hi Risk,

nice one!

Thank you!

Rumi

Mark Symons

The businessweek tipsheet for wikis does have some good stuff. Short but sweet.

For JIRA, is netiquette the right word? Most certainly, it is important to provide guidelines on how to create a good issue. I created a wiki page with a dozen bullets. Here are some samples...

Before logging a new issue, search JIRA to ensure that you are not creating a duplicate.

The Summary should be "Fit to be read by a customer". JIRA allows for semi-automated publication of Release Note based on Issue Summary. So correcting spelling errors, etc, up front means that no one has to go and clean up after you later.

A good Summary is terse.. but not too terse. For instance "Overlapping Columns" is less helpful than "Overlapping Columns in Access Screen".

Annotate your screenshots. Highlight the area of interest and add a note.

Do not attach a 10 MB log: ZIP it first. JIRA v4.x allows you to view files inside ZIP attachments.

Rumceisz

Hi Mark,

many thanks. These are good topics to begin!

Rumi

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira