Hi
I have created epics and in that I have created feature, when I go into scrum board I am able to see epics but not feature, any reason why ? and how do I make feature visible on the scrumboard without create subtask/stories ?
Hi,
I have created Epics, and within them, I have added Features. However, when I check the Scrum board, I can see the Epics but not the Features. Could you let me know why this might be happening? Also, how can I make Features visible on the Scrum board without creating subtasks or stories?
Thank you!
Hi @Kunal checking with you if the field "main delivery team" is present in all the issue types (epic, story, task, subtask) and in case yes, is it always correctly populated?
your filter retrieve only the issues that have the Main delivery team populated.
Another question, do you have "Scriptrunner Enhanced Search " app?
regards
Laura
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Laura Pellizzari based on the filter setting , it is populated everything I need to see , but same is not visible in scrum board , yes i have Scriptrunner Enhanced search app
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a test, I would change your filter to simply be the project and then assess the board. Obviously, you can easily change it back later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can also click on edit filter and see if the feature issues that you expect to be in the board actually show up. Finally do these feature issues showing the backlog possibly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jack Brickey I did checked that , when I setup the filter it showed me everything , but when I go on the board it will only bring subtask and epics
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jack Brickey with just filter as feature and other one is with feature, epic, subtask , I see below
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.
I think I am getting confused here. Based on the issue type icons in your images above it seems to show epics (purple icon) and stories (green icon). Maybe you re-used the story icon for feature? Further I don't see a feature type in your other image of issue type hierarchy. Are you sure that you have a Feature type in this project? When you create a new issue do you see "Feature" in the drop-down?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kunal , if this is a Company managed project please check the board configuration to see if the board's filter might be the reason these issue types are being excluded.
Please feel free to share a screenshot of your board if this doesn't help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Scrum board are designed to provide the hierarchy Epic-Story-Task-Subtask. If you linked the Feature within the Epic (use one of the linking option), the feature cannot be displayed in the Scrum Board as owned by the Epic. Please create Story/task under your Epics to have them displayed correctly in your scrumboard.
regards
Laura
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kunal , what level is the Feature issue type? By default, Jira comes with Epic as a level 1 issue type, and Story as a level 0, subtasks are -1 below Story. I was assuming you created a feature issue type as a level 0. Laura's response gave me pause to question this.
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 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.
Well I guess that is up to you. What does a feature mean in your process? Will a feature include epics or will features be implemented within the context of Epics?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems to me that you need to create a new issue type called feature and set it to level 0. Basically you want a feature to equate to a Story. Please note that a level 0 issue type is intended to be completed within a single sprint. So if a feature takes more than a single sprint. Then you might want to consider using Epic to represent a feature.
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.