-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReleasedBy value of a UserStory is always Null #181
Comments
Do you have some sample code that illustrates the problem? What happens as a result of a query including the condition of either 'ReleasedBy is null' or 'ReleasedBy != null' ? As it looks like 'ReleasedBy' is a custom field, I would not expect the UI to enforce setting that value when a Release value is set, so it is possible that the condition you see is actually "correct" for the scenario where the ReleasedBy value has not been set. |
My requirement is to find out who released the userstory in prod environment. When I get the user story attribute details, "ReleasedBy" is always None. I am expecting the value here because the object has the attribute and it must show the correct value. Sample Code:
Output: |
Thank you for the great info regarding your request! |
I do not see any ReleasedBy field in UI to be updated. Could you please confirm where I can find ReleasedBy field in UI or how pyral package is fetching this attribute value? |
In the Rally subscriptions I have access to (none that are customer subscriptions...) ReleasedBy is not present as a standard field in any entity in the Rally object model. I conjecture that ReleasedBy is a custom field for at least HierarchicalRequirement in the subscription you are working in. As custom field, unless that is referenced in a custom app or on a dashboard created in your organization, there isn't anywhere in the standard Rally application where that attribute is surfaced for display or interaction. |
I am trying to fetch the ReleasedBy Value of a userStory but the object always returns Null Value though the UserStory has been released.
The text was updated successfully, but these errors were encountered: