I'm not sure if this is the intended behavior or not, but one thing I've observed when I was writing my development contribution was the Github project and Pull Request fields were not saved in my drafts.
I know that the site will be revamped, so I'm not sure if this will still be retained. I was planning of creating an analysis contribution, but since steemsql is currently out of sync with the blockchain. I'd like to create a bug hunting contribution for now.
1. Expected behavior
After saving a draft with the Github project and Pull Request fields inputted, move to another page, and selecting the draft from my drafts, the Github project and Pull Request fields should be populated as I saved them.
2. Actual behavior
The Github project and Pull Requests fields were not automatically populated as I saved them
3. How to reproduce
3.1. Pre-requisite
- You must have an open Pull Request in Github for the project you're contributing to. In my case, I have an open PR in busy.org's repository.
3.2. Steps
- Login to https://utopian.io
- Click on
- Select the Development category
- Input the Github project. In this case, I inputted
busyorg/busy. - Select an open Pull Request
- Input the Contribution Title
- Input the body
- Input the necessary tags
- Wait for the autosave function to complete
- Leave the editr by going to another page
- Go to your drafts
- Wait for your drafts to load
- Click on your autosaved contribution
3.3. Result
- Github project and Pull Requests field are not automatically populated based on values when it was auto-saved
Open Source Contribution posted via Utopian.io