[USERSNAP] Application form fields are mistmatched

[dmtrjsg]

Taken at: https://pioneerapp.xyz/#/working-groups/openings/apps-0
Fields:

• Houston, we have a problem.: Application form fields are mistmatched
• Comment: Once I applied for a role, I looked up my application from the opening and went to the "Form" tab to look up what I wrote in the application. However, the headers for questions don't match the values. You can see in the screenshot that the "Tell Us About Yourself" header is mismatched with value from "What is your Discord handle" question. This was application for App WG Lead

Download original image

Browser: Firefox 108 (macOS Catalina)
Screen size: 1728x1117
Browser size: 1670x994
Open #359 in Usersnap

Powered by Usersnap.

[thesan]

The QN data is wrong too:
https://query.joystream.org/graphql

query {
  applicationFormQuestionAnswers (where: { application: { id_in: ["appWorkingGroup-1"] } }) {
   question { question }
    answer
  }
}

{
  "data": {
    "applicationFormQuestionAnswers": [
      {
        "question": {
          "question": "What are ways to identify a new market to enter?"
        },
        "answer": "I'm usually available on demand 9-21 UTC. I could spend up to 10 hrs a week focusing on this role."
      },
      {
        "question": {
          "question": "How would you keep in touch with DApps builders?"
        },
        "answer": "5 years experience as a software developer, have worked for JSG for over 2 years. Have a very deep understanding of Joystream stack, CDN and Atlas (I was the tech lead). Very enthusiastic about crypto and Joystream. I have a lot of experience deploying software, managing Linux servers, etc."
      },
      {
        "question": {
          "question": "Tell us about yourself"
        },
        "answer": "klaudiusz.eth#6880"
      },
      {
        "question": {
          "question": "Your avialability on discord, time range UTC hr/d?"
        },
        "answer": "Discord primarily, potentially jumping on ad-hoc calls if anybody needed more support. GitHub would be the other communication channel."
      },
      {
        "question": {
          "question": "Please mention discord username"
        },
        "answer": "That's a hard question for me to answer since I'm a technical person and business development isn't one of my strong skills. I'm gonna hijack this question though and talk a bit of what I think should be the areas of focus for this WG:\n\n1.  Support any developer wanting to build on top of Joystream. That includes Gleev, other instances of Atlas, but also anyone interested in integrating with our CDN or any other part of the system.\n2.  Make Joystream better accessible to app builders. That would mean preparing reusable libraries / SDKs. Currently to use our CDN you need to have pretty good understanding of how it works and write a bunch of custom code, which will be a blocker for people who would want to quickly prototype.\n3.  Make Joystream operator docs much better. Currently documentation for running different parts of the stack - Joystream node, QN, apps, etc. is quite limited and fragmented. If we want developers to feel confident about building on the platform, we should improve those docs and collect them in a single place so you don't need to know 5 magic links to visit. Not sure if any other WG is supposed to take care of that.\n4.  One idea that's potentially worth exploring - operate infrastructure independent of JSG. That could include QN instance, Pioneer and maybe generic Atlas as well. Currently Joystream is quite dependent on JSG, I think we need to think about a scenario in which the company stops its operations immediately and make sure the project including all services can continue operating without skipping beat. The problem with this one is running infra is inherently centralized in a way - somebody needs to be the domain owner, somebody needs to hold keys to access a server, etc. We would need to think about this to see what the possibilities are.\n5.  Another potential idea - improve integrations with 3rd parties. That could include making sure Joystream has good support in wallets. Also not sure, if there isn't other WG focusing on this.\n\nSo in my head, maybe “integrations” would be a better name for this group than “apps”. I guess it really boils down what the goals for the group should be but above is my take :)"
      }
    ]
  }

[dmtrjsg]

@kdembler was this created via CLI?

[kdembler]

@dmtrjsg No, I applied via Pioneer