We use a python script to transition issues through some interaction with our build system. The workflow is like this: an issue is sent to an Enqueued status, the build machine queries a building project for its Enqueued issues, transitions them to a reserved status while they build, and then transitions them toward QA once they're built.
Our python script manages manages these transitions and also adds a comment with the appropriate build number.
It would be more useful for us if we updated a custom field with the fix build number. However, we ran into an issue implementing this in our python script: it appears as though the custom field can't be accessed or updated.
We were trying to update our custom field using these instructions:
Number field, Global to all issue types, and I did have it on our default screen when we were looking at this. For reference, I used the same configuration as a Label field which is successfully retrieved (but not updated) by the same script.
The Edit Screen is declared in the Screen Scheme, right? That appears to be correctly configured for what we're doing (the field is present on screens associated with the issue type).
Ok, my worry was that it might be a read-only field, or one that disallows edits for some reason. Plus, if it's not on the "Edit" screen, then REST might not have been able to get to it as it respects the ui settings.
I'm afraid I'm stuck, as your code looks like it really should be working.
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