Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to make Jira better

William Dunning
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 1, 2018

I have 2 suggestions to make Jira better.  What is the best way to get these to Jira?

1 - Issues (stories, tasks, etc.) listed in a Kanban board should have a marker if another team member is currently editing the issue.  This will help prevent one team member from saving over another's work if both are editing at the same time.

2  - Issues (stories, tasks, etc.) listed in a Kanban board should have a marker if it has unsaved changes.  It is easy to be flipping between issues and forget to save changes to an issue.

3 answers

2 accepted

0 votes
Answer accepted
Vinu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 2, 2018

Agree with Nic on this. I would like to add a penny.

Like already substantiated, edit of Jira issues are very atomic and I do not see a purpose why there should be a edit marker.

Normally we put in edit markers in document, code repositories where the changes may not be so granular and a page might be in edit for long and hence possibilities for concurrent edits rises.

However in case of Jira and other similar tools these edits are done on the fly and the requirement for a edit marker does not always weigh down the scale.

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 1, 2018

Raise them as suggestions for Atlassian via https://support.atlassian.com/contact

However, I would say you need to flesh this out a bit

How does Jira know someone is editing?  Ok, "they click edit, make some changes, save it" is the process, but you need to define the cases outside that.  Say I click edit, type (but not save yet) changes, wander off to make tea and forget it for a couple of hours. 

At what point do I no longer hold an "edit" over it?  You can't know if I get distracted, bored, close the edit window, change my mind etc.  Currently, the change is atomic and hence absolutely simple - it only matters at the point at which I actually tell Jira "ok, this the change I want to make"

This case extends out into a whole tranche of other problems about concurrency, who may or may not be editing, what you do if people (try to) edit while you think someone else already is, and how you handle potential clashes.

0 votes
William Dunning
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 2, 2018

Thanks Vinubabu and Nic.  I added a suggestion - JRASERVER-68525.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events