Hi devs, In an earlier thread, Joe told me that a reasonable order of priority for implementing the embedding feature would be: Ticket > Milestone > Version > Product > Component > Source > Everything else
I managed to implement the back-end part which deals with embedding tickets, milestones and products (there are some details that I still need to work on, though), but I have some questions regarding versions, components and sources. (By the way, I have committed the code I wrote up to now to the bep_0007_embeddable_objects branch, some feedback would be more than welcome). What does version refer to? Does it cover an entire product? And how can I add or change a version? Also, can different versions of an object be accessed separately through the application? Because I'm not sure how would a user be able to choose to embed a specific version. Or a specific component, for that matter. Also, what would an embeddable source look like? What source information should be embedded? I am not sure how the source feature works in Bloodhound right now, because I didn't quite understand how the repository administration is done. Thanks, Antonia
