impact-space / app Goto Github PK

Description:

In Milestone 1, we want to implement a tagging system for projects. This will allow organizations to categorize their projects more effectively and help users discover and explore projects based on their interests.

Requirements:

1. Create a Tag model with the following attributes:

• Id (Guid)
• Name (String) (required, max length: 128)

2. Create a many-to-many relationship between Tag and Project using an intermediary table ProjectTag with the following attributes:

• ProjectId (Guid)
• Project (Project)
• TagId (Guid)
• Tag (Tag)

3. Develop a UI for organizations to:

• Add, edit, and remove tags associated with their projects
• View tags associated with their projects

4. Implement backend logic to handle CRUD operations for tags.

Acceptance Criteria:

• Tag model is created with the required attributes.
• Many-to-many relationships are established between Tag and Project.
• Organizations can add, edit, and remove tags associated with their projects.
• Backend logic handles CRUD operations for tags.

Notes:

• Please ensure that the UI design is consistent with the overall application design.
• Make sure to properly handle user permissions when allowing access to tags.
• Don't forget to write tests to verify the implemented functionality.

Currently, we are displaying the Skill and Skill Group Management as it's own menu on the non-tenant side.

I think we should move it to the Administration menu, as it seems more appropriate there.

Description:

For Milestone 1, we want to create a setup wizard for organizations (tenants) to configure their organization profiles when they first log in. This will help organizations set up their profiles more efficiently and provide them with a guided onboarding experience.

Requirements:

1. Develop a multi-step setup wizard that guides organizations through the process of configuring their profiles.
2. Include the following steps in the wizard:
   • Basic information (organization name, description, etc.)
   • Organization logo and branding (upload logo, select primary color, etc.)
   • Organization members (invite members, assign roles, etc.)
   • Challenges (define issues that organizations address and issues that organization members actively work towards resolving)
3. Implement backend logic to handle the saving of organization profile configurations.
4. Provide a summary page for organizations to review their settings before finalizing their profiles.

Acceptance Criteria:

• A multi-step setup wizard is created to guide organizations through the profile configuration process.
• The wizard includes steps for basic information, logo and branding, organization members, skills and skill groups, and challenges.
• Backend logic is implemented to handle the saving of organization profile configurations.
• A summary page is provided for organizations to review their settings before finalizing their profiles.

Notes:

• Please ensure that the UI design is consistent with the overall application design.
• Make sure to properly handle user permissions when allowing access to organization profile configurations.
• Don't forget to write tests to verify the implemented functionality.

It's probably best if we moved the FDS documentation to this app repository

The documents for the FDS are located in the docs-dev repository

Description:

As a part of Milestone 1, we need to develop features for organization profiles. The organization profile should include basic information and customization options using the ABP Framework.

Tasks:

• Create a database model for organization profiles using the ABP Framework's Entity Framework Core integration
• Implement the application services for creating, updating, and deleting organization profiles using the ABP Framework's best practices
• Design the UI for organization profile creation, editing, and viewing using the ABP Framework's UI components
• Implement customization options, such as logos and color schemes
• Ensure proper validation and error handling for organization profile data using the ABP Framework's validation system
• Test the organization profile functionality and fix any issues

Acceptance Criteria:

• Users can create, edit, and view organization profiles
• Organization profiles include basic information and customization options
• Proper validation and error handling are in place using the ABP Framework's features

Description:

As a part of Milestone 1, we need to develop organization member profiles that display information about individual members and their skills. This feature will help organizations better understand the expertise of their members and facilitate the assignment of appropriate tasks and responsibilities.

Data Model:

OrganizationMember : AuditedAggregateRoot, IMultiTenant

• Id (Guid)
• Name (String) (required, max length: 128)
• Profile Picture (Attachment)
• OrganizationMemberActivities (ICollection)
• Projects (ICollection)
• AppUserId (Guid?) (Based on AppUser Id)
• Skills (ICollection)
• Organization (Organization)
• TenantId (Guid)

Requirements:

1. Update the OrganizationMember model with the provided data model attributes.

2. Develop a UI for organization members to:

• View their own profile information
• Edit their own profile information (excluding skills)
• Add, edit, and remove skills associated with their profile
• View profiles of other organization members (based on permissions)

3. Implement backend logic to handle CRUD operations for organization member profiles and skills.

Acceptance Criteria:

• - Organization member profiles are created with the required attributes from the provided data model.
• - Organization members can view and edit their own profiles.
• - Organization members can add, edit, and remove skills associated with their profile.
• - Organization members can view profiles of other organization members (based on permissions).
• - Backend logic handles CRUD operations for organization member profiles and skills.

Notes:

• Please ensure that the UI design is consistent with the overall application design.
• Make sure to properly handle user permissions when allowing access to member profiles.
• Don't forget to write tests to verify the implemented functionality.
• Since the Skill and SkillGroup models are already implemented, make sure to use them as needed.

We do not have a logo yet, and right now we are just seeing the "LeptonX" on the left hand menu.

We should also create a favicon.

Description:

In Milestone 1, we want to develop the "Challenges" feature to represent issues that organizations address and issues that organization members actively work towards resolving. This will help organizations and members showcase their focus areas and create a better understanding of their goals and values.

Requirements:

• 1. Create a Challenge model with the following attributes:

• Id (Guid)

• Name (String) (required, max length: 54)

• 2. Create a many-to-many relationship between Challenge and Organization using an intermediary table

OrganizationChallenge with the following attributes:

• OrganizationId (Guid)

• Organization (Organization)

• ChallengeId (Guid)

• Challenge (Challenge)

• 3. Create a many-to-many relationship between Challenge and OrganizationMember using an intermediary table OrganizationMemberChallenge with the following attributes:

• OrganizationMemberId (Guid)

• OrganizationMember (OrganizationMember)

• ChallengeId (Guid)

• Challenge (Challenge)

• 4. Develop Host Challenge Management

• 5. Develop a UI for organizations to:

• Add, edit, and remove challenges associated with their organization

• View challenges associated with their organization

• 6. Develop a UI for organization members to:

• Add, edit, and remove challenges associated with their profile

• View challenges associated with their profile

• 7. Implement backend logic to handle CRUD operations for challenges.

Acceptance Criteria:

• Challenge model is created with the required attributes.
• Many-to-many relationships are established between Challenge and Organization, and Challenge and OrganizationMember.
• Organizations can add, edit, and remove challenges associated with their organization.
• Organization members can add, edit, and remove challenges associated with their profile.
• Backend logic handles CRUD operations for challenges.

Notes:

Please ensure that the UI design is consistent with the overall application design.
Make sure to properly handle user permissions when allowing access to challenges.
Don't forget to write tests to verify the implemented functionality.