Project Custom Fields

[uziyona]

Select Topic Area

Question

Feature Area

Projects

Body

Hi, Is there a plan to add a custom field that will represent Iteration type? The same way that now is available in Issue fields?

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[Thiago-code-lab]

Hi @uziyona,

Currently, the Iteration field type is unique to GitHub Projects and is not yet available as a standalone Issue Custom Field (at the repository or organization level).

While you can create Text, Number, Date, and Single Select fields directly on Issues (visible in the right sidebar even outside a Project), the "Iteration" logic—which automatically handles date ranges, "current," and "next" scopes—is still tied specifically to the Project infrastructure.

Workarounds:

Use the Projects sidebar: If you link the Issue to a Project, you can see and edit the Project's Iteration field from the "Projects" section of the Issue sidebar.

Single Select Field: If you need a "sprint" field that lives natively on the Issue (independent of a Project), the closest alternative right now is creating a Single Select custom field, though you lose the automatic date logic.

To track if this is coming, I recommend keeping an eye on the GitHub Public Roadmap.

[uziyona]

Hi @Thiago-code-lab
Thank you for the prompt respond!

I thought Issues field is defined at org level and then applicable to all projects and pinned Issues.

Can you add it as feature request? Iteration is a key element in planning, and as it is available in project level, i think it should be also on org level.

Not sure i understand your workaround:

Workarounds:

Use the Projects sidebar: If you link the Issue to a Project, you can see and edit the Project's Iteration field from the "Projects" section of the Issue sidebar.

[dbuzatto]

To add to the previous reply:

At the moment, the Iteration field type is tightly coupled to GitHub Projects and isn’t available as a standalone Issue custom field.

If your goal is to replicate iteration behavior outside a Project, a few workarounds are:

• Use a Single Select issue field (e.g., Sprint 1, Sprint 2, etc.) and manage values manually.
• Use Milestones if you want date-bound grouping tied to releases.
• Use labels for lightweight iteration tagging (e.g., sprint-24, sprint-25).

However, none of these options replicate the automatic date-range handling and “current/next” logic that Iteration fields provide inside Projects.

If iteration logic at the Issue level is important for your workflow, it may be worth submitting this as a formal feature request via GitHub Feedback.

Right now, Iterations remain a Project-scoped feature.

[DinukaEk]

At the moment, Projects (new) custom fields don’t support an “Iteration” field type, and there hasn’t been an official announcement confirming that this specific field type is on the public roadmap.

The currently available custom field types are limited to things like:

• text
• number
• single select
• date
• iteration (only for built-in system use, not as a user-defined custom field)

So while you can use the built-in Iteration field, you can’t create your own custom field that behaves the same way as the native Iteration type for Issues.

[pankajrawat24]

Hi @uziyona

Right now, the Iteration field is still limited to GitHub Projects and isn’t available as a custom field on Issues at the repository or organization level.

So while you can create custom Issue fields like text, number, date, or single-select, the Iteration type (with automatic date ranges and “current/next” handling) only works inside Projects.

Workarounds for now:

• Link the Issue to a Project and manage the Iteration from the Projects section in the Issue sidebar

• Use a Single Select field (e.g., Sprint 1, Sprint 2) if you need something directly on the Issue

• Or use Milestones/labels for basic sprint grouping

But none of these fully replace the built-in Iteration behavior.

As of now, there’s no public confirmation that Iteration fields will be available as standalone Issue custom fields, so the best option is to keep an eye on the GitHub public roadmap or submit a feature request.

[uziyona]

thanks @pankajrawat24 - how can i submit a feature request?

[pankajrawat24]

You can submit a feature request through GitHub Community Discussions - that’s the current way GitHub collects product feedback.

go to - https://github.com/orgs/community/discussions

• Search first to see if someone already suggested it
• If not, click New discussion
• Choose the relevant category (like Projects) and describe your idea and use case

Other users can upvote or comment, which helps the GitHub team see interest. You can also track updates on the GitHub public roadmap.