I have the situation where a user can set a field on a requirement and this triggers some other software to replicate that requirement within a JIRA project.
This works well.
I'm now trying to solve a problem where I want to be able to identify objects in JIRA which are no longer being controlled from JAMA. Essentially where a user in JAMA might set this export field to 'JIRA-ABC' one day, this results in a replicated requirement in JIRA project ABC, but then subsequently changing this field to JIRA-XYZ, resulting in a new replicated requirement in JIRA project XYZ.
I want to be able to identify the requirement in JIRA project ABC.
After some thought I think I can achieve this by having a field on my JAMA requirements which is always the current date / time. I would then be able to sync this across to JIRA and I could achieve my goal by simply querying objects where this field is not within a few minutes of current date and time.
My problem is that I cannot see a way to include this date field and have it auto populated? Is this achievable please?
Hi Jason,I think this could only work if the objects in Jama were subjected to regular updates. The reality is they might only be updated periodically.I suppose this could be overcome by doing a bulk update once in while which would update the modified value of all artefacts. Is there a quick and easy to do this?Thanks,Andy.
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204