When a job is submitted from Cumin, the "description" value is used to look up submission objects in MRG Grid. If no submission object exists with that submission description, a new submission object will be created that is owned by the submitting user.
If a submission object already exists with that description, the new job will become part of the existing submission. However, the existing submission object may be owned by a different user.
Submissions in Cumin are sorted by description and filtered by owner in the "Grid User" view. The submission list under "Grid User->Submissions" will only show submission objects owned by the logged in user.
If a user submits a job with a description that matches an existing submission object owned by another user, the user will not be able to see their new submission in the "Grid User" view in Cumin.
Users may adopt a convention to help avoid submission description duplication. For example, users my add "_username" to the end of all description values when submitting to create unique identifiers.
Alternatively, the "Administrator" view in Cumin may be used since it does not suffer from this problem (all submissions are visible regardless of owner). This is only practical if role enforcement is disabled or the 'admin' role is granted to large number of users (effectively disabling role enforcement).
A suitable convention for description values based on username should eliminate most if not all cases of description duplication.
Disabling role enforcement solves the problem if the 'Administrator' views are used, but it removes the advantages of role enforcement. All users will have administrator privileges and the list of submissions will not be filtered to the logged in user.