I have some text fields that are generated and updated using REST api.
The problem is that people are not always aware that these fields are generated and they may try to edit them, wondering days later why their change was overriden.
How can I solve this?
Note: I tried to hide the fields but if I hide them I will not be able to edit them using REST.
I don't think there's an easy way to do this. Either a field is available for edit, or it is not.
Some thoughts include:
Use the "restricted edit" trick. For each status, add a transition to the workflow - one that does not change the status. Make it go through a screen that includes your fields, and put conditions on it so that only the user who does things via REST can use the transition. Remove the fields from all edit screens that the other people use. Possibly a total pain to code for, because your REST app will now need to work out and perform a workflow transition rather than an edit.
Write new fields that know when they can be edited.
I did not mention global transitions at all.
Although I can see my posting didn't explicitly say you have to do this separately for EACH status.
I would have mentioned them, if I didn't already know that they wouldn't work, but I apologise for being thoroughly unclear on that! I should know better and been explicit.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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