[$125] Changing the isAvailable attribute value is not changing the actual status

[Vips19]

Screenshots

Reproduction Steps:

Open the Application https://skill-search.topcoder-dev.com/
Click Topcoder > Go to first tab
Click Click Edit for User Brady Swift
Now change the isAvailable custom attribute and check the status is changing or not

Actual Result: Changing the custom attribute is not changing the actual status of the user

Expected Result: Changing the custom attribute must change the actual status of the user

Device/OS: Laptop | Windows 8.1 (64bit)

Browser Information: IE11,Chrome,Firefox

[callmekatootie]

Good catch. Let me check if the two are the same attributes or not and get back

[callmekatootie]

Will take this as a bug - the attribute should NOT have been seen here because it already has a UI element and not meant for custom attributes section.. Applicable to other attributes too for which we already have other ui elements

[wdprice]

@callmekatootie confirming that I believe availability should not appear in custom attributes

[callmekatootie]

Expected:

We currently have the following four environment variables used by front end:

• REACT_APP_ATTRIBUTE_ID_LOCATION
• REACT_APP_ATTRIBUTE_ID_COMPANY
• REACT_APP_ATTRIBUTE_ID_TITLE
• REACT_APP_ATTRIBUTE_ID_ISAVAILABLE

Currently, the point to GUIDs. Instead, we intend to update them to use the following values:

• REACT_APP_ATTRIBUTE_ID_LOCATION='location'
• REACT_APP_ATTRIBUTE_ID_COMPANY='company'
• REACT_APP_ATTRIBUTE_ID_TITLE='title'
• REACT_APP_ATTRIBUTE_ID_ISAVAILABLE='isAvailable'

Task 1
When the landing page loads, the user is prompted to select the org. We then proceed to fetch the attribute groups for that org (https://api.topcoder-dev.com/v5/attributeGroups?organizationId=<the_selected_org_id>) followed by fetching the attributes in each of the attribute groups (https://api.topcoder-dev.com/v5/attributes?attributeGroupId=).

At this point, isolate the "standard user attributes" and the "company attributes". Standard user attributes are the ones defined in the above env variables (we will be defining their name as seen above - currently, we defined their GUID which will be replaced with the name instead). The company attributes are already being isolated - isolate the standard attributes too. Isolate here means identify - just like how we identify the company attributes (and display them in the Manage Filters modal).

The relevant code is here. At least I think that is the code - PLEASE VERIFY before you proceed with the fix.

Task 2
Having identified the primary attributes (particularly their ids), you will then proceed to use it at all locations where we earlier used the standard user attributes. That is, earlier, we used the ids of the attributes in the code - you will now use the ids too, but only after first identifying them through Task 1.

This will ensure that the standard user attributes DO NOT show up in the Edit Profile modal, under the custom attributes section

This also means that you would need to ensure that you first fetch the attributes AFTER which you will then carry out the search

For your testing, you could instead use the names of the existing custom attributes instead (gender, experience etc) and verify that they are not showing up in the Custom attributes section (and the filter).

PLEASE PROCEED WITH CARE This is a critical issue of the app and thus, please make sure that any changes that you do are not having any side effects

[cwdcwd]

Contest https://www.topcoder.com/challenges/30134274 has been created for this ticket.

This is an automated message for lazybaer via Topcoder X

[cwdcwd]

Contest https://www.topcoder.com/challenges/30134274 has been updated - it has been assigned to callmekatootie.

This is an automated message for lazybaer via Topcoder X

[callmekatootie]

This ticket is open for pickup

[cwdcwd]

Contest https://www.topcoder.com/challenges/30134274 has been updated - it has been assigned to Timor.

This is an automated message for lazybaer via Topcoder X

[cwdcwd]

Contest https://www.topcoder.com/challenges/30134274 has been updated - it has been assigned to Narekvar90.

This is an automated message for lazybaer via Topcoder X

[callmekatootie]

@narekcat This one's another critical issue... Also I understand the effort involved so you can take 36 hours more if needed (assuming you do intend to submit a solution)

[narekcat]

@callmekatootie . Ok, I am actively working on this issue. Thank you for additional hours. I'll submit my solution in time.

[narekcat]

@callmekatootie . I approximately finished this issue, but I have a question. Need I show 'General Attributes' in 'Manage Filters Modal' or 'General Attributes' must be replaced with 'Standard Attributes'?

[callmekatootie]

@narekcat You mean the title of the section? The current one is fine... I just referred it as Standard attributes because the code did (and the UI called it General instead 🤷‍♂️ )

[narekcat]

@callmekatootie One more question. How I must get suggestion data for Company and Title. Can I mock that data like Locations and Achievements or I must add endpoint to back end like skills ?

[callmekatootie]

Company and title will NOT be part of the filters - so no suggestion is needed... I realize that I described it such that you would believe that these need to show up in the standard / general attribute filters - but they will not... they are standard / general attributes, but we will not have any filters for them...

[narekcat]

@callmekatootie . I have fixed this issue. Please see pull request #612.

[cwdcwd]

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30134274

This is an automated message for lazybaer via Topcoder X