Good evening!
I've built a Confiform in Confluence with 600+ fields and have built a view for someone to open the form for a pre-existing issue. The bulk of the fields are populating the "Description" section of the JIRA issue.
What I'm hoping to do is find a way to only show what fields were updated in the History of the issue while maintaining the master view with the most up to date records. Is this possible? might I need to create 2 IFTTT macros to do this? Any help would be appreciated.
Hi
Isn't it so that the Jira history data is maintained by the Jira itself and updating the fields in Jira will update Jira history data automatically?
What I am trying to say that updating the description field will show you exactly what has been changed with the update
Alex
Thanks for the quick response Alex. I think what I'm looking for might be trying to get the best of both worlds.
I have analysts navigating a form with hundreds of fields and let's say they only update 2 or 3. I have my "Update JIRA Issue" IFTTT macro set to capture every possible field as there's no way to know what the analyst might update. This makes for a very long list in my History and it's difficult to isolate what was updated.
Perhaps I need 2 IFTTT Macros? One to capture all possible fields that could be updated and one to only show the updated fields? Is that possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, I see
It means that when you update via IFTTT Jira takes it as new values for all the fields, even if they have not been changed during the update and puts them in the history log
Probably you can adopt this concept - https://wiki.vertuna.com/display/CONFIFORMS/Sending+the+change+log+via+email
for the JSON you construct to update the Jira issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.