Uncategorized

Other

6 sections
20 source tickets

Last synthesized: 2026-02-13 02:52 | Model: gpt-5-mini
Table of Contents

1. Retrospective student qualification addition (CeMAP Bridge)

1 tickets

2. Payments, refunds and allocation handling (ELCAS, membership direct debit, vendor invoices)

3 tickets

3. Fulfilment and dispatch anomalies (Carousel/MOSAS stock & missing order transmission)

2 tickets

4. Requests outside team remit and ticket reassignment

10 tickets

5. Asset and CMDB updates, manual fixes, and document template edits

3 tickets

6. Jira field default-value limitation and workaround

1 tickets

1. Retrospective student qualification addition (CeMAP Bridge)
95% confidence
Problem Pattern

Student requested retrospective award/recording of a CeMAP Bridge qualification that has no certificate on file because supporting FPC1 evidence was not provided at the time; qualification is no longer offered and records are missing from the Student Records system.

Solution

Support confirmed retrospective addition of the CeMAP Bridge was permitted when eligibility evidence (the original FPC1 certificate) was provided. The team accepted provided FPC1 evidence as proof of completion and added the CeMAP Bridge qualification into the Student Records Qualifications module so the student record reflected the historical award.

Source Tickets (1)
2. Payments, refunds and allocation handling (ELCAS, membership direct debit, vendor invoices)
80% confidence
Problem Pattern

Questions and discrepancies about refunds, credit-note/invoice allocations and Direct Debit behaviour: students overpaid contributions when course structures changed; uncertainty how to represent refunds/credits and allocate incoming remittances in the finance/student ledger; membership DD clawbacks created outstanding balances and required clarification about how new DDs are invoiced.

Solution

For the ELCAS/DipFA–CeMAP case support reconciled and reallocated credit notes and invoices in OASIS to represent the student refund and MOD/DBS remittance: a credit note was unallocated from one invoice and reallocated to the correct invoice reference so the refund/credit and journal entries matched the entitlement (invoice and credit-note identifiers were adjusted in the student finance records). For the Messenger People vendor invoice the Product Owner/Accounting accepted responsibility and handled the outstanding payment under the standard 45‑day terms; IT clarified its role was limited to user provisioning. The membership Direct Debit query was recorded as a billing behavior question in the ticket and no definitive system-side resolution was logged in the ticket record.

3. Fulfilment and dispatch anomalies (Carousel/MOSAS stock & missing order transmission)
80% confidence
Problem Pattern

Students who registered while a textbook SKU was out of stock were routed to a 'dues' holding pot and did not appear on the Carousel despatch file when stock was later added; orders/labels were also reported missing where the Carousel label number did not appear in exports, causing undelivered textbooks.

Solution

Investigation identified that registrations created during stockouts were placed into the 'dues' holding pot and that backlog entries were not automatically released when stock was replenished; consequently some registrations did not appear on Carousel despatch exports. It was also noted that label numbers for orders were only generated when the export file was sent, so absence of a label in the Carousel file indicated the order file had not been transmitted to the fulfilment partner. The findings were recorded to explain the missing dispatches and missing label records.

Source Tickets (2)
4. Requests outside team remit and ticket reassignment
90% confidence
Problem Pattern

Users submitted requests or reported incidents to IT that belonged to other teams or systems — e.g., exam access/registration queries, HR/payments and employment-certificate requests, procurement or vendor booking and invoicing queries (including training/course quotes and purchase orders), application/process gaps blocking data imports (CARE bookings), facility/HVAC faults, or requests to change approvers or reassign tickets when owners were unavailable. Common symptoms were wrong recipient/misrouting, missing contract/registration numbers from external vendors, process gaps preventing imports, localized building faults, and the need to reassign approval responsibilities.

Solution

Tickets that were outside the handling team’s remit were redirected or escalated to the appropriate owners and recorded; tickets were marked Done once reassignment or referral was completed. Specific actions taken included:

• Exam access and registration queries were referred to the exam office (akad-pruefungsamt@iu.org).
• FS Marketplace display issues were forwarded to the Lecturer & Course Coordination (LCC) service portal.
• Employment-certificate requests were forwarded to HR/internal HR contacts.
• A training/course quotation misrouted to Procurement was clarified as a training booking/HR matter; the requester was informed that trainings were handled by HR or could be booked directly via the provider, and that a purchase order should be created in advance if a company purchase was required and invoices should be sent to the organisation’s invoice mailbox.
• Additional consultancy invoicing and booking changes for a Mathplan contract were forwarded to Application & Lifecycle Management (ALM); ALM acknowledged the requirement for a specialised import route to bring bookings from CARE and took ownership for further handling.
• An approver change requested because of parental leave was applied to the open request, comments were added to the ticket, and the task was closed.
• A missing contract/registration number for a Deutsche Bahn subscription order was identified as a vendor verification/abo issue; the user was informed that issuance and verification were performed by the vendor/abo centre (and HR/booking channels) rather than IT.
• A localized heating/HVAC fault in a Learning Area was referred to Real Estate Services (facility management) for HVAC intervention.
• Questions about honoraria for guest lecturers were noted as outside IT responsibility and were referred to the relevant academic/administrative or finance office for contracts and payments.
Additionally, an old unresponded ticket was reassigned after the original owner was identified as departed under the Minerva programme. All referrals and reassignments were noted in ticket comments before tickets were closed.

5. Asset and CMDB updates, manual fixes, and document template edits
95% confidence
Problem Pattern

Requests to create or change site/asset records, to reassign asset locations where the UI did not permit saving, and to edit content in document templates (e.g., outdated contact details on certificates).

Solution

The team created the requested site object in the CMDB/Jira Assets with the provided site fields (IU Mainz, code MAI3, site manager and full address) and recorded the asset link. Where the site/location UI prevented saving an assignment, support performed a manual reassignment of the asset record (AL Sora Pazer) to the correct site. For certificate content, the outdated phone number was removed from the 'Pathway - Completion Certificate' and 'Pathway - Participation Certificate' templates in Study Organization > Documents and the updated templates were saved.

Source Tickets (3)
6. Jira field default-value limitation and workaround
90% confidence
Problem Pattern

User requested a native default (prefilled) text value for the Jira Issue Description field on a specific board; Jira's Description field did not accept a native default value and the user queried permission changes or alternative approaches.

Solution

Support confirmed that Jira does not support a native default value in the Description field. A non-code workaround was used instead: the team recommended populating the Description via an automation rule or a canned response on issue creation so that the field appeared prefilled to users without changing core Jira permissions or field types.

Source Tickets (1)
Back to Summaries
An unhandled error has occurred. Reload X