- **status**: unassigned --> accepted
- **assigned_to**: Praveen
- **Milestone**: future --> 4.3.3
---
** [tickets:#867] No clarity on assignments of dependents when sponsor has no
CSIs**
**Status:** accepted
**Milestone:** 4.3.3
**Created:** Tue Apr 22, 2014 10:27 AM UTC by surender khetavath
**Last Updated:** Tue Apr 22, 2014 10:27 AM UTC
**Owner:** Praveen
changeset : 5143
model : 2n
case:
1) configure any 2n model having 3sis
2) lock the SIs. create dependency SI1<-SI2<-SI3.
3) if there are any csis in SI1 delete them
4) unlock SI3/SI2/SI1 resp.
As SI1 has no CSIs, it will be unassigned. And due to dependency dependents
also remain unassigned. But the system is healthy i.e SUs,comps,sg everything
is up and running. There is no log/document suggesting what should happen with
assignments.
It gives wrong perception, that system is healthy but no work load assigned.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets