Because you asked me.
My personal concerns are mainly the gui is so awefull to use, that i dont want to use it. As from a developer perspective it is not possible to do thing fast in/with jira. If i want to open a subtask in a tab, i have to choos the subtask form the board, then it will open a side split where it opens the task, but i need another action to open the subtask in a tab. In general, the implementation of a sprint overview is kinda suboptimal.
This side pane thingy is so buggy, i cannot count how often i lost content because of unwanted reloads. And then it doesnt provide all the actions you need, so you guess it you have to open it in a tab anyway...
Managing dependencies,or links to other issues/stories is overcomplicated and waste time in the way how its gui wise implemented.
The search. Its a whole different story of awefullness, because you find nothing, if you dont have a degree in this comical query language.
And then the markup what they use. Why they invented an another markup dialect?
If you ping persons and jira is linked up with AD and you have to edit it again it used the short AD id, which is in our case one letter with four numbers (eg. a1234). yes they get resolved, but that steels the possiblity to do something semi automated.
I as developer want to interact with a bugtracking/scrum tracking tool as less as possible. If i have to, then it should be as fast and convinient as possible. The Jira gui does not provide this.
That's why i implemented some helper scripts, that i can do all the changes or actions within a keystroke, while i dont have to left my (vim) environment.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Because you asked me.
My personal concerns are mainly the gui is so awefull to use, that i dont want to use it. As from a developer perspective it is not possible to do thing fast in/with jira. If i want to open a subtask in a tab, i have to choos the subtask form the board, then it will open a side split where it opens the task, but i need another action to open the subtask in a tab. In general, the implementation of a sprint overview is kinda suboptimal.
This side pane thingy is so buggy, i cannot count how often i lost content because of unwanted reloads. And then it doesnt provide all the actions you need, so you guess it you have to open it in a tab anyway...
Managing dependencies,or links to other issues/stories is overcomplicated and waste time in the way how its gui wise implemented.
The search. Its a whole different story of awefullness, because you find nothing, if you dont have a degree in this comical query language.
And then the markup what they use. Why they invented an another markup dialect?
If you ping persons and jira is linked up with AD and you have to edit it again it used the short AD id, which is in our case one letter with four numbers (eg. a1234). yes they get resolved, but that steels the possiblity to do something semi automated.
I as developer want to interact with a bugtracking/scrum tracking tool as less as possible. If i have to, then it should be as fast and convinient as possible. The Jira gui does not provide this.
That's why i implemented some helper scripts, that i can do all the changes or actions within a keystroke, while i dont have to left my (vim) environment.