When I think of components, I think of additional characterizations I can apply to an issue to track which components of my software solution might be impacted by an issue, or to provide context to another developer so they are aware of what code they will need to look toward in providing detail or corrective action based on that ticket. Instead, I create a component and I see it in my backlog of issues.
If my way of thinking on this is wrong, is there a better way to make these kinds of characterizations that is organized and "simple" to do?
For further education, if my way of thinking is in fact flawed for the design intent of components, can someone tell me what other advantage they would have to the organization of a board?
This is not built in functionality of a Software Kanban project.
If you want to continue exploring this, can you recount the steps you went through to create the Kanban project? Maybe it is something to do with the type of project you selected (i.e. Software vs. Work Management).
Not sure I am following exactly what you are saying. Your first few sentences lined up with how I view Components as well. But then you said, "Instead, I created a component ...". Not sure what you would create the component as an issue if it runs counter to how you think components should be used.
Do you have exact examples?
Here's an example from my end. Developers are building an App or a Feature. It might be for iOS or Android or Browser, etc. So those are my components. iOS works gets tagged with the iOS component for that issue. That way I can run reports of all the work done for iOS or Android or whatever component is attached to the work.
Are we saying the same thing?
Thanks for the response. What I'm trying to convey is not about what I am doing, its about some assumption I think Jira is making that imposes the moniker of "issue" to a component when it is created. This ultimately leads to the actual question of...
Why is a component showing up in my boards backlog of issues?
Because I don't see a component as an issue but as I suggested, rather a means of better organizing issues. So to recreate what I am seeing, quite simply:
I hope that explains it better.
Me too...hence the inquiry. Of course I'm left wondering if I'm doing something wrong, some setting, some overlooked configuration ? Does your confusion suggest that when you create a component, you DON'T see it in your backlog of issues? Could this be because it's a kanban board and not some other configuration?
As you can see...I'm a bit befuddled but clearly don't want my issues log being mucked up with items that are not actually issues.
When viewing the list of issues, I can add this to the filter..
AND type IN ("Bug", "Story", "Task") ORDER BY created DESC
and my components disappear...which of course makes sense because I'm filtering OUT Epic types.
It should be noted that the project is a "Software project' and that I don't have an option, when I create the component, to indicate a "type"...Epic is being set by default.
Sorry...trying to find as much more information as I can get some help in understanding.
So if you are going to the project and clicking on the Components link on the right side, which brings up the list of Components on that project. Then you are clicking on the Create Component button and add a component.
And you are saying that if you follow that path, when you create the component that it is actually creating an Epic on that project????
If that's the case - is there anyway you can shoot a video of that?
Also, if you look at the history of the Epic, who does it say created it?
Hello @Mike Craig
Can you tell us the exact steps you followed to "create the component"? Also, are you working with a Team Managed or Company Managed project?
For a Company Managed project, Components can be created only by an Administrator of the project, and they are created by navigating to the Components screen (an option in the navigation pane on the left). When this is done, the value becomes available for selection in the Components field of the issues in the project. It does not create a new issue in the project.
That Components functionality does not actually exist for Team Managed projects at this time. See https://jira.atlassian.com/browse/JSWCLOUD-17601
So, if you tell us exactly what steps you took to create the "component" we can better address your question.
Um...you just described the exact steps. This is a company managed project, I enter the project space, click components from the navigation, click the create component button, provide a name and description and save it.
Then, I click the issues navigation link (or the kanban board link) and there amongst my issues are the components I've created, all indicated as type "epic".
Jira simply does not do this on its own. Creating an issue when a Component is added is not a built-in function of the product. It does not happen in my instance.
I understand that you did not interactively create the Epic. One was created nonetheless. I'm wondering what Jira recorded in the Epic's history as the user that created it.
Are you a Jira Administrator for this instance? Can you check if there are Global Automation rules that may be causing this? I'm not sure if you'll be able to see Global Rules if you are not a Jira Administrator (vs. a Project Administrator).
Do you have any apps added to your Jira instance? Do you have any Webhooks or Listeners set up for the instance? You won't be able to see that information unless you are a Jira Administrator.
Well, then a miracle is happening here because when I create a component, this is exactly what is happening because I'm looking right at it. The history for the "epic" only shows that I created it...which again, I did not ever create an epic, I created a component.
I am the administrator, if there are default automation rules, they may be employed but if they were default, then you'd be experiencing what I'm experiencing. Everything is default...I've made no environment changes, added no apps, no webhooks no nothing.
I seem to be repeating myself alot and no one seems to be able to replicate what I'm seeing so either I'm describing it wrong, which at this point I find hard to believe or everyone else has some automation in place that is doing something I am not.
I did not think this was going to be quite so challenging a question.
I wish I could upload a video so you could see that is nothing magical I'm doing and this is all happening in a very fresh environment. Generally I have so few developers to help me, we don't need apps and webhooks and automation tasks...small shop, very simple needs...though when I administrated in a larger company, these things did not happen...but even there, I don't think we were fully using the power of Jira properly and I wanted that to be different in this project/job.
So, starting from scratch, I created a company administrated scrum software project and the same steps do NOT produce an issue from the creation of a component...so it would seem this is some kind of function of Kanban that I'm not familiar with.
Easily solved then, I'll go back to scrum project types which I'm apparently more familiar with.
Thanks to everyone who sat with this for a minute...my take away is stick with what I know.
When I asked about Automation Rules, I was asking about Global Rules which would be applicable to all projects in your instance. There is not a concept of "default" Automation Rules that would be applicable to all Jira instances.
This should not be happening even in a Kanban (vs. Scrum) project.
I'm not contesting that you are having the experience. I'm trying to figure out why you are having the experience when nobody else does.
If you want to continue working through this to try to discover what happened, I would ask the following questions.
1. If you create another Kanban project the exact same way, does the same thing happen?
2. Can you walk us through the steps you went through when creating the project?
3. Since we (other users in the community) cannot access your instance, have you opened a support ticket directly with Atlassian to allow them to connect to your instance and investigate the issue?
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events