Skip to main content

Submit Request For Change(RFC)

Updated over a month ago

Welcome to the iLost IT help desk Request for Change (RFC) procedure.

iLost offers one of the most user-friendly Lost and Found software solution globally. Our IT team continuously enhances and develops our software, incorporating valuable insights from our partners experiences. This approach ensures that iLost remains effective and adaptable for each partner's unique needs.

Given iLost's wide-ranging application across various markets and segments, we recognize that your organization may have specific requirements. To address these needs and further optimize the iLost software for your use, we provide a Request for Change (RFC) procedure. This process allows us to collaborate with you on potential system modifications, tailoring the software to better align with your organizational objectives.

*Before you begin, it's important to understand that submitting an RFC is a non-binding action.

Here's what you can expect:

  1. When you submit a request, the iLost IT help desk team will carefully review it to assess its feasibility and potential impact;

  2. If the request is deemed feasible and realistic, our IT team will develop an estimated quote based on the required development hours;

  3. This quote will be sent to you for approval before any work begins;

    From now on the RFC is a binding action:

  4. Mutual approved? From this step the RFC is a binding agreement. iLost IT help desk will schedule the development work based on our current roadmap and the urgency of your request;

  5. Once the development is complete, we test it collaboratively with you. If the development is approved, we proceed to close the RFC case.

This process ensures that we can effectively manage resources, prioritize tasks, and provide you with a clear understanding of the scope and timeline for your requested change. Please note that submitting an RFC does not guarantee immediate implementation, but rather initiates a collaborative process to evaluate and potentially realize your proposed changes.

Now, let's walk through the steps to submit your Request for Change using the Jira Service Desk portal.

Submitting a Request for Change to iLost IT Help Desk

To submit a Request for Change (RFC) to the iLost IT help desk team, follow these steps using the Jira Service Desk portal:

  1. Go to the iLost Jira Service Desk portal by clicking here;

  2. Select ''Common requests''

  3. Fill out the RFC form with the following information:
    - Raise this request on behalf of
    - Problem/Idea summary: Provide a concise summary of the change
    - Description: Explain the proposed change in detail
    - Justification: Outline the reasons for the change
    - Attach any relevant documents or diagrams to support your request
    - Add urgency of this development
    - Add impact on the Lost and Found process

  4. Review your submission for accuracy and completeness

  5. Click "Send" to send your Request for Change to the iLost IT help desk team.

After submission, you'll receive a confirmation email with a ticket number. The IT team will review your request and may contact you for additional information or clarification.

Tracking Your Request

To monitor the progress of your RFC:

  1. Log in to the Jira Service Desk portal.

  2. Navigate to the "My Requests" or "Requests" section.

  3. Locate your RFC using the ticket number or title.

  4. Click on the request to view its current status and any updates.

Development Sprint Packages(per 40-hour / €4,000,-)

The iLost development process is flexible and tailored to your project's scope. iLost provides development sprint packages available in 40-hour increments for a fixed price of €4,000,-. This can be applied to a single large project or distributed across multiple smaller development requests, depending on your specific requirements. If you plan to submit change requests throughout the year, we recommend budgeting annually for a sprint package.

To accommodate custom requirements or desired features, we provide development sprint packages that include:

  • 40 hours of dedicated work

  • Comprehensive project management

  • Detailed specification and planning

  • Custom development

  • Thorough testing

  • Seamless release integration

For urgent changes or additional assistance, contact the iLost IT help desk team directly through the provided communication channels in the Jira portal.

Did this answer your question?