parse-community / parse-community/parse-dashboard
Enhance _JobStatus data vizualization and exploration
Open
Nobody has claimed this yet.
type:feature
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
- Browsing a
Pointer<_JobStatus>sends to a blank page

- Core > Jobs > Job Status (http://localhost:1337/dashboard/apps/my-app/jobs/status) does not show job's
paramsand content is cropped.

Feature / Enhancement Description
I would like to view _JobStatus in Core > Browser the same way I can see User. In order to :
- browse to a
Pointer<_JobStatus> - see every columns of the JobStatus object
Example Use Case
Alternatives / Workarounds
- Use the /jobs/status page and filter by objectId : when clicking a
Pointer<_JobStatus>then redirect tojobs/status/${the_job_status_object_id}+ add columns + set the size of the columns based on its content - Add an option (in
ParseDashboardconfig) to list which "Predefined Classes" should be displayed in the Core > Browser. Thought: some classes may be not editable at all (for safety)
3rd Party References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing Core > Browser handling of User objects with the _JobStatus pointer case, then inspect the /dashboard/apps/my-app/jobs/status view and its objectId route. Confirm how the jobs/status page renders params and columns. Done means a Pointer<_JobStatus> opens its object and the Job Status view shows all relevant fields without cropping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100