feat(custom-fields): template pre-fill + feed generator migration #494

Merged

jmiller merged 5 commits from feat/issue-template-custom-fields into dev 2026-06-05 03:15:20 +00:00

Conversation 0 Commits 5 Files Changed 13

+303 -108

jmiller commented 2026-06-05 02:49:39 +00:00

Owner

Copy Link

Copy Source

Summary

• #493: Issue templates can specify custom_fields in YAML frontmatter to pre-fill org-level custom field values when creating issues. Works in both web form and API.
• #492 Phase 3: All six feed generators (Joomla, WordPress, Composer, Drupal, PrestaShop, WHMCS) now resolve extension metadata from org-level repo-scoped custom fields first, falling back to the update_stream_config table, then repo-derived defaults.
• Fix: Issue sidebar now loads org-level issue-scoped fields instead of legacy repo-level fields.

Test plan

• Create an issue template with custom_fields: frontmatter, verify fields are pre-selected in the new issue form
• Submit a new issue from that template, verify custom field values are saved
• API: POST /repos/{owner}/{repo}/issues with custom_fields map, verify values saved
• Set repo-scoped custom field values via Settings > Metadata, verify update XML feeds use those values
• Verify feeds still work correctly for repos without custom field values (config table fallback)
• Verify feeds still work correctly for repos with neither custom fields nor config (defaults)

Closes #493
Ref #492

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

?? Generated with Claude Code

## Summary - **#493**: Issue templates can specify `custom_fields` in YAML frontmatter to pre-fill org-level custom field values when creating issues. Works in both web form and API. - **#492 Phase 3**: All six feed generators (Joomla, WordPress, Composer, Drupal, PrestaShop, WHMCS) now resolve extension metadata from org-level repo-scoped custom fields first, falling back to the `update_stream_config` table, then repo-derived defaults. - **Fix**: Issue sidebar now loads org-level issue-scoped fields instead of legacy repo-level fields. ## Test plan - [ ] Create an issue template with `custom_fields:` frontmatter, verify fields are pre-selected in the new issue form - [ ] Submit a new issue from that template, verify custom field values are saved - [ ] API: POST `/repos/{owner}/{repo}/issues` with `custom_fields` map, verify values saved - [ ] Set repo-scoped custom field values via Settings > Metadata, verify update XML feeds use those values - [ ] Verify feeds still work correctly for repos without custom field values (config table fallback) - [ ] Verify feeds still work correctly for repos with neither custom fields nor config (defaults) Closes #493 Ref #492 _Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>_ ?? Generated with [Claude Code](https://claude.com/claude-code)

jmiller added 2 commits 2026-06-05 02:49:40 +00:00

feat(custom-fields): pre-fill custom fields from issue template YAML frontmatter ... 9ebe1b26b1

Add `custom_fields` map to IssueTemplate struct so templates can specify
default values (e.g. `Priority: Medium`). On new issue form, org-level
issue-scoped fields appear in the sidebar with template defaults pre-selected.
NewIssuePost saves the values after issue creation. The API create issue
endpoint also accepts `custom_fields` by name.

Closes #493

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

feat(updateserver): resolve extension metadata from custom fields with config fallback ... 1935889f6b

Add resolveExtensionMetadata() with cascading priority: org-level
repo-scoped custom fields → update_stream_config table → repo-derived
defaults. All six feed generators (Joomla, WordPress, Composer, Drupal,
PrestaShop, WHMCS) now use this unified resolver. Repos can be migrated
to custom fields gradually since the config table remains as fallback.

Ref #492

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

jmiller added 1 commit 2026-06-05 02:53:12 +00:00

docs(changelog): add #492 and #493 entries ... b72f88e78b

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

jmiller added 1 commit 2026-06-05 03:01:00 +00:00

fix(custom-fields): address code review findings ... cd4c701cb6

- API: return 500 on GetCustomFieldsByOwner failure instead of silently
  swallowing the error
- resolveExtensionMetadata: add DownloadGating/KeyPrefix to metadata
  struct instead of mutating the caller's cfg pointer (side effect)
- resolveExtensionMetadata: add Description custom field mapping
- Composer: use meta.PHPMinimum instead of bypassing the cascade
- Web form: flash error on custom field save failure instead of silent log

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

jmiller added 1 commit 2026-06-05 03:14:30 +00:00

fix(custom-fields): log errors instead of silently discarding them ... 8e0388c9d8

- saveCustomFieldsFromForm: log GetCustomFieldsByOwner errors
- resolveExtensionMetadata: log DB errors on custom field lookup
- NewIssue/ViewIssue: log errors from GetCustomFieldsByOwner and
  GetCustomFieldValuesMap instead of blank-assigning
- Composer: fix misleading comment about override source

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

jmiller merged commit 5ca1c888c0 into dev 2026-06-05 03:15:20 +00:00

jmiller deleted branch feat/issue-template-custom-fields 2026-06-05 03:15:21 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

breaking-change

Breaking API or behavior change

ci-cd

CI/CD pipeline changes

config

Configuration changes

dependencies

Dependency updates

deploy-failure

Deployment failed

docker

Docker/container changes

documentation

Documentation changes

good first issue

Good for newcomers

health-check

Repo health check result

help wanted

Extra attention needed

mokostandards

Related to MokoStandards framework

push-failure

Git push operation failed

security

Security vulnerability or hardening

size/l

200-500 lines changed

size/m

50-200 lines changed

size/s

10-50 lines changed

size/xl

500+ lines changed

size/xs

< 10 lines changed

standards-drift

Deviates from MokoStandards

standards-update

MokoStandards compliance update

sync-failure

Sync or mirror failed

tech-debt

Technical debt and TODO/FIXME items

upstream

upstream

Inherited from upstream Gitea

work-in-progress

Draft or incomplete work

bug

Something is not working

chore

Maintenance and housekeeping

documentation

Documentation improvements

enhancement

Improvement to existing functionality

feature

New feature or request

pending: dependency

Blocked by another issue or external dependency

pending: deployment

Tested and approved, awaiting deployment to production

pending: design

Needs UI/UX or architecture design before implementation

pending: documentation

Feature works, needs documentation/wiki update

pending: feedback

Awaiting feedback or decision from stakeholder

pending: review

Implementation complete, awaiting code review

pending: testing

Feature implemented but not yet tested

priority: critical

Must fix immediately

priority: high

Should fix soon

priority: low

Nice to have

priority: medium

Fix when convenient

refactor

Code restructuring without behavior change

roadmap

Planned feature or enhancement tracked on the roadmap

scope: client

Client-specific work

scope: dolibarr

Dolibarr modules and customizations

scope: infrastructure

Server, CI, backups, monitoring

scope: joomla

Joomla templates and extensions

scope: waas

MokoWaaS platform

security

Security vulnerability or hardening

status: blocked

Waiting on external dependency

status: duplicate

Duplicate of another issue

status: in-progress

Being worked on

status: needs-review

Ready for review

status: wontfix

Will not be addressed

No labels

Type —

Status —

Priority —

Milestone

No items

No Milestone

Assignees

Clear assignees

jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#494