# How do I adjust workflows from Jira? (task points, card view)

**URL:** <https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931>\
**Category:** Improve your Agile with Taiga\
**Tags:** agile, scrum, kanban\
**Created:** [March 22, 2023, 8:50pm UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931 "2023-03-22T20:50:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\
**Post date:** [March 28, 2023, 11:25am UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/4 "2023-03-28T11:25:06Z")

</div>

I answe you below each question.

> Can stories belong to multiple epics?

Yes, a user story can belong to several epics.

> Could we use regular epics and sprint dummy epics together? Trying it out it seems like you can but is it intended behavior? Might it cause any issues?

Yes, in every way a dummy sprint epic would be a regular epic one, and its intended behavior is to be closed when all its contained user stories are also closed. It shouldn’t cause any issue as long as you know how the epics work.

I recommend you to create a demo project recreating your needs by using different approaches (fake sprint epics, sprint swimlanes, estimation tags, kanban/scrum… ), in order to choose the one that offer less friction to your team in their daily operations.

You may find interesting these links about the epic user stories:

> [@What is an epic story?](https://community.taiga.io/t/what-is-an-epic-story/172):
>
> According to the inventors of agile, an EPIC story is a large undefined user story that must be subdivided. [EPIC Stories] Photo Credit: [Kulawat Wongsaroj](http://www.infoq.com/author/Kulawat-Wongsaroj) from the post [Visualizing the Big Picture of your Agile Project](http://www.infoq.com/articles/visualize-big-picture-agile). An EPIC must be broken down into smaller user stories. As far as I recall, user stories should follow the “INVEST” pattern where “I” stands for “independent” and “V” for “valuable”. In my opinion, an EPIC can make sense and be visible, perhaps in a different color so as to re…

> [@What’s an Epic? Our research](https://community.taiga.io/t/what-s-an-epic-our-research/132):
>
> If you work with agile methodologies, you’ve surely heard about epics. Epics are hard to define, because there isn’t an official definition, and if you ask around you’ll see that not everyone shares a unique idea of what an epic is. But if you watch how people use epics you can get a clue about them. Say you’re defining a user story. While doing so, you realize how diffuse everything is, you still don’t have all the information, the story is too big and it will take more than one sprint… “Diffu…

> [@The Epics/Wiki/Meetup, icing on the cake](https://community.taiga.io/t/the-epics-wiki-meetup-icing-on-the-cake/126#taiga-epics-module-a-powerful-tool-in-the-right-hands-3):
>
> Those “little” extras that can make a huge different to you project. Part of the beauty of using Taiga is that you can hypersimple and then build your way up by using more features or more modules. This entry on Taiga Resources will cover three less critical modules that could make your team’s life so much easier… Taiga Meetup module Let’s start with least impressive of all three but still a convenient add-on for quick project-based video rooms. Und…

---

_[View the full topic](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931)._
