Re: [PR] rework project, allocation and member management [airavata-custos]

["lahirujayathilake (via GitHub)" <gi...@apache.org>]

lahirujayathilake commented on PR #639:
URL: https://github.com/apache/airavata-custos/pull/639#issuecomment-6250552155

   The changes looks good @yasithdev
   
   Some minor comments on the UI/UX
   
   1. 
   <img width="3424" height="1588" alt="image" src="https://github.com/user-attachments/assets/5ad9fce1-2e4c-4b6f-a0bc-195f6d2acc06" />
   
   - Better to bring the email below the name how it used to be
   - For some external allocation providers there's only one active allocation at a given time. So I think it would be better to indicate that
   - We don't need the 'created date' inside the card, do we? because it is already in the header row. We should avoid the duplications
   
   2. I like this separation among internal and external allocations. 
   <img width="3438" height="1378" alt="image" src="https://github.com/user-attachments/assets/edd59889-21a8-4700-b60a-72d05bf00ff1" />
   
   - internal allocations should also indicate the cluster and rest of the fields. We shouldn't make these internal allocations to be active without having an end date. 
   - what's the "LOCAL-1" tag below the internal allocation?
   - I think we should make all these to be consistent regardless internal or external. I'd suggest to have the "internal", "ACCESS", etc tag next to the allocation name (what you've already designed) so we can easily spot the upstream source
   
   Let me know what you think about these suggestions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@airavata.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org