# 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:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![RT-AP](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@RT-AP](https://community.taiga.io/u/RT-AP)\
**Post date:** [March 22, 2023, 8:50pm UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/1 "2023-03-22T20:50:56Z")

</div>

Hi I’m helping a team transition from Jira to a local Taiga instance.  
They’re having some serious problems transitioning due to disruptions  
to their workflow from features Taiga doesn’t seem to support support.

Is there any way these features can be added as a custom config/plugin?  
Is there any chance of these features being implemented anytime soon?

If not what do you think is the best workaround?

1. They use tasks with points that sum up to story points automatically.  
I saw a bug report on task points but it didn’t seem to be implemented.  
Any chance of task points being added anytime soon?  
Can we use a custom field for task points and if we do can we get it to show up on the cards/summary  
and can we automatically sum custom task points into story points?

2. Although they are working with sprints they find the Kanban view more useful a lot of the time.  
Is there a way to filter kanban by sprint? (or at least by last change time?)  
Is there a way to make the Sprint view more like the Kanban view?

---

<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 27, 2023, 9:05am UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/2 "2023-03-27T09:05:43Z")

</div>

Hi @RT-AP

We’re very happy you chose Taiga in your transition from Jira, and we really hope to provide some support in the process of translating their workflows.

Reviewing your comment, I’m sure you’ve already found by yourself [this related topic](https://github.com/taigaio/taiga-front/issues/569) covering the aspirational purposes of the [user stories in Taiga](https://community.taiga.io/t/user-stories-demystified/104). You can also consider reading this in-deep review covering [the process of estimating in Taiga](https://community.taiga.io/t/5-different-methods-to-estimate-in-agile-part-i/818)

Although we don’t intend to add any further features to Taiga6, we’ll consider your requirements for the next evolution we’re currently developing, [Taiga Next](https://community.taiga.io/t/important-update-on-taiganext-and-kaleidos/171).

An now, the workarounds we suggest you to try:

1. While it’s not an intended usage, an easy way to simulate task points and make it appear in the summary sprint board, is by adding **Tags** to the tasks.  
You simply have to associate a new colored tag with the estimation points you consider to use to a task, and they’ll be displayed in the “Expanded view” as shown in the following image:

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/7bcb151cef79136ca6e4a384428aba71387cf65b.png)

1. We propose you two ways of simulating sprints in the Kanban view:

- First option would be to use **Swimlanes** representing real sprints. They can be collapsed/un-collapsed at will to have a clearer Kanban view hiding unwanted/previous sprints.
- Another workaround would be to use **Epics** representing real sprints, then adding your user stories to the matching sprint Epic, and finally filtering the Epics (spints) from the Kanban’s board filters.  
This way the board would just display user stories belonging to the selected epics (sprints).  
Please, remember to first enable the “Epic” module from the Settings panel (Settings \> Project \> Modules \> Epics)  
 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/48ddce936a909794eebd870b8672943fbeccbec2.png)

We hope to have offered some help in your migration from Jira.

---

<div class="post-metadata">

**Author:** ![RT-AP](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@RT-AP](https://community.taiga.io/u/RT-AP)\
**Post date:** [March 27, 2023, 5:42pm UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/3 "2023-03-27T17:42:43Z")

</div>

Can stories belong to multiple 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?

---

<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…

---

<div class="post-metadata">

**Author:** ![debbra](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/debbra/32/870_2.png) [@debbra](https://community.taiga.io/u/debbra)\
**Post date:** [April 7, 2023, 9:43am UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/5 "2023-04-07T09:43:46Z")

</div>

I find that going to the project itself is easier to change the workflow.

---

<div class="post-metadata">

**Author:** ![RT-AP](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@RT-AP](https://community.taiga.io/u/RT-AP)\
**Post date:** [April 7, 2023, 8:26pm UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/6 "2023-04-07T20:26:21Z")

</div>

are there apis to read task tags(for points)/get stories in a sprint and set story points/epics a story belongs to?

Also are there webhooks so we could do this on task tag change/story added to sprint change?

---

<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:** [April 11, 2023, 6:48am UTC](https://community.taiga.io/t/how-do-i-adjust-workflows-from-jira-task-points-card-view/931/7 "2023-04-11T06:48:49Z")

</div>

> [@RT-AP](#):
>
> get stories

Hi @RT-AP

Yes there’s an API you can use to recover the information you require, if not directly, indirectly making nested requests. Please, refer to our [Taiga REST API](https://docs.taiga.io/api.html) documentation.  
Just a quick tip, a `sprint` as we know it, it’s really a `milestone` in the API language.

And regarding your second question, you can also configure the webhooks in your project, from Project → Settings → Integrations → Webhooks

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/80fad9e66bf56c78bb7cc3342e8a0c1d8d735f7e.png)

You can read the documentation about [Webhooks](https://docs.taiga.io/#webhooks) to know about how to configure them and its payloads.

Once enabled, Taiga emits a http POST to the configured URL whenever:

- a sprint is created, updated or deleted.
- a user story is created, updated or deleted.
- a task is created, updated or deleted.
- an issue is created, updated or deleted.
- a wiki page is created, updated or deleted.

For example, the payload data when a task is updated, would include its latest tags in the “data” key:

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/37fd6dad341f7a6e6b9a80221d05020f8f5e8179.png)

I hope it helps.
