Skip to content
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

Cannot get planned_in from requirement #68

Open
yuxisun1217 opened this issue Apr 25, 2022 · 8 comments
Open

Cannot get planned_in from requirement #68

yuxisun1217 opened this issue Apr 25, 2022 · 8 comments

Comments

@yuxisun1217
Copy link
Contributor

yuxisun1217 commented Apr 25, 2022

When I get planned_in in a requirement, it can show a Plan object in the list, but all the attributions are empty.

Python 2.7.5 (default, Jun 11 2019, 14:33:56) 
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from pylero.work_item import Requirement
>>> wi = Requirement('PLANXXX', 'ITEM-41685')
>>> pl = wi.planned_in
>>> pl
[<pylero.plan.Plan object at 0x7f048ca7f990>]
>>> pl.name
>>> pl.plan_id
>>> pl.description
@leelavg
Copy link
Collaborator

leelavg commented Apr 25, 2022

@yuxisun1217

  • could you pls rebase, I think Fix planned_in issue #58 #59 should fix this issue.
  • in worst case this might be a regression due to above fix, was this working earlier?

@yuxisun1217
Copy link
Contributor Author

Thanks @leelavg!
I just confirmed that this fix is in my module.
At first I use pip install pylero to install it, and the Requirement planned_in is an empty list (although there is a planned in the polarion UI).
Then yesterday I removed this module, cloned the main branch code, built it as a rpm package and installed. And then I can see the Plan object in the planned_in list, but this object cannot see name, description and any other attributions.

@leelavg
Copy link
Collaborator

leelavg commented Apr 25, 2022

  • ack, thanks for confirmation
  • as asked earlier, was this working earlier at any point of time that you know of?
  • so, the PR fixed one issue and need to look how to get attrs populated

@yuxisun1217
Copy link
Contributor Author

Hi @leelavg ,

This is the first time I use the Requirement module so I don't know if it worked well at any point of time. Sorry cannot help :(

@yuxisun1217
Copy link
Contributor Author

yuxisun1217 commented Apr 25, 2022

>>> wi._suds_object.plannedInURIs
(ArrayOfSubterraURI){
   SubterraURI[] = 
      "subterra:data-service:objects:/default/XXXX${Plan}XXX_XXXX_Release",
 }

@leelavg
Copy link
Collaborator

leelavg commented Apr 25, 2022

  • we better not provide these details on github issues, would you pls mention only the required bits and mask identifiable info in those snippets as well 😅

@yuxisun1217
Copy link
Contributor Author

@leelavg Oops! Updated. Thanks for reminding!

And may I have another question: is there any way to add/remove a plan into a requirement? Thanks!

@leelavg
Copy link
Collaborator

leelavg commented Apr 25, 2022

  • I wasn't sure of what to make out from the snippet of SubterraURI 😅

is there any way to add/remove a plan into a requirement

  • need to check the code as I'm not an avid user of Polarion these days

@yuxisun1217 yuxisun1217 changed the title Cannot get planned_in from requrement Cannot get planned_in from requirement Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants