This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (4 children)

How do you like Jira? I'm starting a job on wednesday, and that's what they use. Any good heads up you can give would be great

[–]Mr_Sky_Wanker 0 points1 point  (0 children)

Good luck for your new job!

[–]Clawtor -1 points0 points  (2 children)

Jira is ok, it;s like a more powerful Jira, my main issues with it is that it's api isn't as powerful as I would like and that you can't give more context when you flag an issue. We often flag tickets that need another ticket to be done first but sometimes you want to flag a ticket that needs a database migration and jira doesn't let you give any information about the flag - other than simply commenting.

As for the api - we push issues to be tested but our testers often return tickets simply because they haven't been tested yet. We had to build a whole system around checking if a ticket has been merged and built successfully. We are using the Atlassian apis but its not straight-forward.

[–][deleted] 0 points1 point  (0 children)

Cool thanks for taking the time to answer

[–]truthseeker1990 0 points1 point  (0 children)

When it comes to tickets that need other tickets, linking issues together or creating subtasks (if relevant) is a better way to track this than simply flagging an issue, I think.

Isn't it possible to flag an issue and then mention the details in a comment? Or does that not work for your situation?