We have a project for which we have a associated a create screen. In create screen we have added the description field,but in edit screen we have not added the description field. My question is some of our users are complaining about this by saying they should have description field in edit sceen as well,since they might need to add some extra lines to description, but our problem is if we add description field in the edit screen they will be able to edit description meaning if someone has added some description while creating a issue we will be able edit that description while editing the issue since decription field would be active. What is the best method to solve this issue.
That is the good part about JIRA as a tracking tool, all changes to the description field will be recorded. See in the History tab under Activity.
So if you add description to the edit screen and someone changes the description you are still able to see the original description.
There is no issue here - fields are supposed to be editable, that's what they're for. There are reasons to make some not-editable of course, but you need to agree those reasons with your users. It sounds like you need to allow edit because they need to do it.
Note that this is exactly what the history is for - if someone edits a field, all changes are recorded, so you can't actually lose information anyway.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs