joomla / joomla/jissues

JIssues posted to the wrong project

Open
#486 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
73
Forks
79
Avg merge
1d 5h
Merged PRs (30d)
8

Description

Steps to reproduce the issue
  1. Go to http://issues.joomla.org/tracker/jtracker/425 and write a comment, but don't submit.
  2. In a new tab, go to http://issues.joomla.org/projects
  3. Select Joomla! CMS
  4. Go back to the tab that has open http://issues.joomla.org/tracker/jtracker/425 open and submit.
  5. My guess is that it will post it at https://github.com/joomla/joomla-cms/pull/425
Expected result

For #5, it should post it at https://github.com/joomla/jissues/pull/425

Actual result

For #5, it posts it at https://github.com/joomla/joomla-cms/pull/425

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reproduction flow at issues.joomla.org/tracker/jtracker/425 and the projects page, especially what happens after selecting Joomla! CMS in one tab and submitting from the other. Trace the project selection used during submission and compare the expected jissues pull-request destination with the actual joomla-cms destination. Done means the comment or pull request is posted to the project selected when the submission page was opened.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.