[Abdelrhman1326]

Documentation-first PR for #132, as discussed in the issue. It documents the Bugzilla CSV export, the proposed field and status mapping, and the known limitations. No code changes.

Refs #132

[jesperpedersen]

@sksingh2005 Can you take this one ?

[sksingh2005]

Sure. Will have a look

[sksingh2005]

Thanks @Abdelrhman1326 docs-first looks good, and I verified the mapping against both billetsys' import pipeline and the Bugzilla 5.0/5.2 source. The field mapping, status mapping (lower(status) = 'closed' filter), duplicates, and requester fallback all match the code. Three corrections before merge:

1. columnlist replaces, not appends. "Extra columns can be requested" reads as if &columnlist=opendate,bug_severity adds columns — it actually drops every default column, including short_desc. Please show a full columnlist in one example URL and warn explicitly.
2. Version claims are wrong: these behaviors exist in 5.0, not 5.2+. Verified in both 5.0 and 5.2 sources:

• the leading space ( ---) is added by the CSV filter for any value starting with - (also = + @), not just resolution
• \ → ＼ (U+FF3C) is applied for logged-in users in 5.0 too

Suggest dropping the "5.2 and later" qualifiers.
3. Base URL optionality is missing, contradicting what we agreed in #132: filled → external_issue_link = base URL + show_bug.cgi?id= + bug_id; left empty → external_issue_link stays empty (traceable via source_key and the "Imported from Bugzilla bug #101" line). Please document that in the Import section.
Two optional nits: mention billetsys' 5 MB upload cap next to the 10000-bug truncation limitation (makes "split per product" doubly necessary), and state what the created_at timezone conversion targets — the pipeline only accepts ISO T timestamps, so the adapter must reformat Bugzilla's YYYY-MM-DD HH:MM:SS.
Good work, these are doc fixes only.

[sksingh2005]

@Abdelrhman1326 Rebase is also needed

[Abdelrhman1326]

Thanks for the review! @sksingh2005 I’ll rebase the branch and push the new commit very soon with all three corrections (columnlist replace behavior, dropping the “5.2+” qualifiers, base URL optionality) plus the two optional nits (5 MB cap, created_at format).

[Abdelrhman1326]

@sksingh2005, @jesperpedersen I pushed the changes, and all three corrections and both nits are in:

1. columnlist is now documented as replacing the default columns, with a full example URL.
2. The "5.2 and later" qualifiers are removed.
3. The Bugzilla base URL is documented as optional in the Import section and the field mapping.
4. The 5 MB upload cap is mentioned next to the 10000-bug limit.
5. The created_at mapping now says the value is reformatted to an ISO T timestamp.

I also merged main to resolve the AUTHORS conflict. Ready for another look.

[sksingh2005]

@Abdelrhman1326 rebase

[jesperpedersen]

@Abdelrhman1326 Remember to always rebase and squash. You can use orangu to help you.

[Abdelrhman1326]

@sksingh2005 @jesperpedersen rebased onto main and squashed into one commit. Ready for another look.

[sksingh2005]

Thanks @Abdelrhman1326! The updates look great and all review points are addressed.
Just one quick repo-convention item before merging: please also add your name to doc/manual/en/97-acknowledgement.md under Authors so it stays in sync with AUTHORS (and optionally drop the literal ＼ glyph in 60-import.md to keep XeLaTeX happy).

[Abdelrhman1326]

Thanks @sksingh2005 for the re-review!

I've added my name and email to the Authors section in doc/manual/en/97-acknowledgement.md, fetched the latest changes from upstream main, rebased my branch, and committed and pushed the updates.

[sksingh2005]

@Abdelrhman1326 Squash the commit into single one

[Abdelrhman1326]

Done @sksingh2005 .

[sksingh2005]

LGTM! Approving the documentation and mapping specification. You can now go ahead with the code implementation in a follow-up PR.

[sksingh2005]

Merged.
Thanks for your contribution. Welcome in our community

[Abdelrhman1326]

Thanks @sksingh2005 for merging and for the warm welcome! Now that the proposal is in, I'll start working on the implementation. Midterms are next week, so I'll be balancing this implementation alongside my exam schedule and will post updates as I make progress on the PR, thanks again for the warm welcome!

[sksingh2005]

Sure. Take your time. Let us know when you stuck somewhere. Discussions are open as always. All the best.