I want users to be able to quickly create subtasks and enter the critical data as they create. Then I found this...The SCS project is a team-managed (next-gen) project. In this project type, Jira has a specific design limitation: The system "Original Estimate" field is intentionally excluded from the "Create" screen.
Why would you intentionally exclude such an important field from the create screen and give me no option to add it back? This makes zero sense and once again I find myself confounded by the extreme limitations of team managed projects and Rovo telling me to move my project to company managed which is not an option. What is the point of team managed project if I can't actually manage them?
Hello @Xenia Chilkowich
Where did you find that design limitation documented?
I had no problem adding the Original Estimate field to the Layout for a Subtask in a team-managed Software space.
In order for the Original Estimate field to display in the Create dialog (the pop-up, not the inline subtask creation mode) you must have the Estimates feature turned on for your project and set to Time.
I agree with @Trudy P Claspill If Time Estimates are enabled and the Original Estimate field is added to the subtask layout, it should appear in the full Create dialog for team-managed projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have all the proper settings. i am trying to add the information I found but this screen keeps rejecting it saying there is html in there which there is not.
"Team-managed projects manage all fields in a single master layout, but hide certain fields from the create process if they aren't marked as visible context field"
Adding it to the description section didn't work for me and that makes a big mess of my page layout. And this answer makes zero sense because other fields that aren't in the context area DO appear when I create.
I can't add it to the create screen scheme because this is not a company managed project. See attached screenshot
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Xenia Chilkowich
Can you confirm for us the type of space with which you are working? Please click the ... (ellipsis) button next to the space name in the navigation panel on the left. Please share a screen image of the pop-up that displays. Example:
Specifically I'm looking for the last two lines; i.e.
Software space
Team-managed
Can you provide a screen image from the Features section of Space Settings for the space, like the image I provided in my earlier response, showing the Estimation setting?
Can you provide a full screen image of where you are at when you get this message?
"Team-managed projects manage all fields in a single master layout, but hide certain fields from the create process if they aren't marked as visible context field"
It is possible that there are functional differences between my environment and your environment due to the way Atlassian rolls out changes. The screen images requested will help us determine that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using a software space team-managed project. Team manged projects have incredible limitations vs company managed projects so I already know things look different for both of us. You could solve this in a company managed project but updating the create scheme but I cannot.
My feature screen is identical to yours with the same settings checked.
I am not getting an error message, I am simply sharing my findings when I researched this topic. The original estimate field just doesn't appear when I create, only after I save it. No error, it just doesn't appear.
This is everything that I found when I asked if it will let me share it.
It can feel incredibly inconsistent that some Context fields show up on your team-managed Create screen while others—like Original Estimate—are completely hidden.This happens due to a mix of Jira's default formatting rules, user settings, and how Jira handles text vs. system fields:Field Type Formatting (Text vs. Metadata): In Jira, fields that allow long text (like Description, Environment, or custom paragraph fields) cannot live in the right-hand context sidebar. Even if Jira groups them under "Context fields" in the project backend, the system recognizes them as primary content fields and forces them onto the Create screen so you don't miss writing crucial details.The "Hide when empty" Rule: By default, Jira applies a "Hide when empty" rule to secondary metadata fields (like Original Estimate, Labels, or Components). Because a brand-new issue has no data in it yet, Jira treats Original Estimate as an empty field and hides it to keep the creation form clean.Global vs. Project Field Defaults: When Jira administrators or apps add new global custom fields, Jira frequently defaults to sticking them into every project's Create screen automatically. System fields like Original Estimate do not get this automatic treatment; they must be explicitly mapped to the visible creation block.Personal Create Screen Filters: Jira allows individual users to filter their own Create screens. If you or someone else previously clicked Configure fields inside a Create pop-up and chose "Custom" or deselecting "All", Jira will selectively hide system fields like Time Tracking while continuing to show other fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Xenia,
Thank you for that additional information.
"Team-managed projects manage all fields in a single master layout, but hide certain fields from the create process if they aren't marked as visible context field"
If you are relying on an AI tool for that information, AI tools frequently provide incorrect information because they reference outdated material, or other material that has misinformation.
What happens when you actually try to add the Original Estimate field to the layout of your Subtask in your Team-managed Software space?
As I mentioned, I had no problem adding the field to my Subtask in my project.
And, as evidenced by the following layout for another work item type in the same space, all work items types within such a space do not share their layouts.
And finally, as can be seen in this image, the Original Estimate field does display in the Subtask create screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suspect because you are in a company managed project an admin added this to your create screen scheme. This is not an option for me. thanks anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My screen images are not from a Company-managed project. These are all images from a Team-managed Software project.
And I have the Organization Admin, Site Admin, Billing Admin, and Jira Application Admin for this environment.
The functionality to add this to your Team-managed project should be available to you are assigned to the Administrator role for that project.
If you want to continue to explore your scenario and try to figure out why you are having difficulty let us know. If you don't want to spend more time on it, that's also your perogative.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is the layout screen for subtasks. I even tried moving it into the non context section per the instructions I found. Here is the screen when I create a subtask. Original Estimate is nowhere to be found.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On the other hand, the Label field which I have under hide if empty as well as Stakeholder and Cloud do show up. It's like the create is totally ignoring my issue layout
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try adding the Time Tracking field to you Subtask layout. That is the difference I see between your screens and my screens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have both Time Tracking and Original Estimate in the Layout for subtasks?
Can you go here in the Create dialog:
Make sure "Hide unused fields" is disabled. The click the Configure fields option and make sure that the Time Tracking field is checked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok I just removed and added it back to the page layout and saved it and this time it WORKED You are a genius, thank you!
For some reason configure fields works for me for all issue types but when I try it on a subtask it throws an error that just says something has gone wrong.
Thanks for your persistent trouble shooting :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.