| Pages: 1 :: [one page] |
|
|
| Author |
Thread Statistics | Show CCP posts - 1 post(s) |
KA24DERT
TeamPlayers
Negative-Feedback
635
   |
Posted - 2014.09.23 00:23:00 -
[1] - Quote
There any chance at allowing read-only Jira access?
Or maybe submitting Jira tickets/comments via CPM members? |
Atiim
12404
|
Posted - 2014.09.23 00:44:00 -
[2] - Quote
You're better off asking a GM via Help Ticket.
The 1st Matari Commando
-HAND
|
Maken Tosch
DUST University
Ivy League
9518
|
Posted - 2014.09.23 01:24:00 -
[3] - Quote
I think I'm ignorant. What is Jira? Or is that a typo and you meant Jita?
On Twitter: @HilmarVeigar #greenlightlegion #dust514 players are waiting.
|
|
CCP Rattati
C C P
C C P Alliance
7789
|
Posted - 2014.09.23 04:08:00 -
[4] - Quote
Maken Tosch wrote:I think I'm ignorant. What is Jira? Or is that a typo and you meant Jita?
Ongoing joke, I forgot to delete my working comments from the spreadsheet 
"As well as stupid, Rattati is incredibly slow and accident-prone, and cannot even swim"
|
|
Avallo Kantor
SHAKING BABIES
FACTION WARFARE ALLIANCE
411
|
Posted - 2014.09.23 04:52:00 -
[5] - Quote
Jira is a ticket service for development.
Basically: Lots of development work is split into manageable chunks called tickets.
A ticket might be a bug, a part (or a whole) feature, an enhancement, etc.
Tickets can be given values (normally expressed in about how many days it takes to complete) as well as being put into different storys / epics (Such as feature X might be put into it's own epic)
You can put the tickets into sprints (great for agile development) as well as having different categories (To-do, working, code review, testing, merging, done) that allows easy understanding of when tickets need other people to take action on them.
Not to mention other useful features such as comments, graphs, and the ability to link to git, have pictures, etc.
TLDR: It's Software Development tools. |
Avallo Kantor
SHAKING BABIES
FACTION WARFARE ALLIANCE
411
|
Posted - 2014.09.23 04:59:00 -
[6] - Quote
On topic though, generally Jira tickets are written in a way that developers understand, or are written in a more "technical" manner. (At least where I work)
That way a developer doesn't have to waste time looking at a ticket that says "I crashed when I opened my fitting page"
That conveys no real information, as there are any number of ways to reproduce that action that does not cause a crash. Generally tickets from users are horrible amalgams of confusion, whining, and entitlement.
Again, at least where I work, we have a guy in charge of "translating" tickets from users to jira tickets, as well as reproducing them, commenting on them, and in general helping to "fix them up" so that a developer can get to work on it without wasting potentially hours of a day just trying to see if the ticket can even be reproduced in the first place. |
|
|
| |
|
| Pages: 1 :: [one page] |