h4. Guidelines for making a proper JIRA issue. h5.

Before you make an issue When you make a proposal for a change-request or improvement, or even a new tool, make sure your direct colleagues and the other people who are working with this tool feel the same way about it. Otherwise there is always the chance that we will change it to your satisfaction, but in the next version we need to change it again for another person's view upon the matter. Save yourself and others the disappointment, us the extra work, and make sure everyone (that matters) supports the changes / additions you request. When you find a bug, create a bug-report with a professional attitude. Bugs are part of software development. You're bound to run into them. There is never a need to elevate your anger, disappointment or frustration in a bug-report. Bug-reports should be neutral, and free from sarcasm, shouting (capitals) and many exclamation or question marks. You will ruin the mood of the developer who enthusiastically took on the responsibility of fixing the bug, and we are sure you didn't mean to do that. h5. Making the issue Making an issue according to the description below will help us greatly, and speed up bug-fixing. Also, it will minimize misunderstanding and misinterpretation, so you will have the issue fixed in the way you want it to be fixed (if possible). # Specify the correct *issue type*, we mostly use ** Bug (a bug is an error (not always on the screen of course), not something which you want to work differently) ** New feature (a new tool / report) ** Improvement (changes which enhance the working procedure, or the user experience) ** Request for change (something is working as intended, but you would like it to work differently) # Give a clear description in the *summary* ** Bad: mouseover does not work ** Good: content management / q&a search / mouse over on hint icon does not work # *Priority* is not important for us ** Critical bugs with work no work-around or complex work-around will be patched ** Other issues have low priority # Put the *due date* in about 2 weeks, (issues will be rescheduled according to releases / patches) # Specify the version you detected the bug in (*affected version*) # Leave the *fixed version* _empty_ (it will be set by development, depending on releases / patches) # Fill out the *environment* details ** Environment it took place on (live, staging) ** Browser (+ version) you used when this event occurred # Specify a clear *description* ** Customer *** Bad: "any Dutch customer", or "KLM" *** Good: "klm_it" ** Are you able to reproduce it yourself? Does it happen all the time, or irregularly? ** What action do you have to do to reproduce it? ** What did you expect? ** What do you see? ** If you can name specifics, please do (question id, a certain string which causes the error, certain selection options in a report, a certain symbol you have entered, etc) ** Screen-shot (_full screen_, no partial shots, no cut-outs)

reportimage. Label Issue If you're creating an issue for a missing label. Your Development Team thanks you for your assistance. please first make a search with the label name on JIRA to check if an issue for this label hasn't already been created.** If you have a file in which the error occurs. attach it (exported report. etc) # All other fields will be handled by us Of course not all items are appropriate in each situation. h5. If you don't find any result please name the issue (in summary) : " *Missing Label : MISSING_LABEL_NAME* " h5. . but please fill out as many as you can. XML packet.

Sign up to vote on this title
UsefulNot useful