Labels not inherited and selected sprint is neglected when creating a story

[Patrik Wallin]

Hi,

We're having some issues when creating new stories in upcoming sprints.

Usually when a quick filter is selected (based on a label) the story will inherit that label automatically. That doesn't happen anymore.

Also the selected sprint is ignored and the created story will show up in the backlog instead.

Anyone experiencing same issue or may know where the problem is? 

Thanks

[Patrik Wallin]

@Jack Brickey :

Yes so let me explain the quick filter. In my Scrum Board I have set up Quick filters to filter stories with specific labels e.g. "labels = X". When I press that filter in the backlog, the backlog filters on all stories with the label 'X'. Usually when having that filter applied to the backlog, any new story created would inherit a.k.a automatically be assigned with label 'X'. This is no longer happening. 

Regarding the sprint issue, yes you're correct

[Jack Brickey]

Hi Patrick. I may not be following you here but it seems you must have some automation going on that now seems to be acting up.

you mention selecting a quick filter. What do you mean by this exactly? In my mind selecting a filter is an action taken on an active sprint so you can filter the displayed issues, e.g. “my issues”. I’m not sure what action you are doing that would result in a label being added to the issue but I suspect some automation or maybe a post function is involved?

Now for the other part of your issue, it seems you are saying that when creating an issue and if you enter an active or future sprint it doesn’t “stick”. That is the issue does not show in the active or future sprint. Is that correct?

[Jack Brickey]

So good news is that I learned something new today. It is always a good day when I learn. I never knew that creating an issue from a board would inherit based upon the filter. 

So I tested on my instance and indeed it worked. Now the question is, why does your not. One very real possibility and my bet is that you are on a different version and either it is a regression in functionality or possibly that functionality is going away. I think it would be worth testing this on a couple of different projects on your side and if doesn’t work on any then contact Atlassian Support directly.

[Patrik Wallin]

Glad that I could help!

I have tested on different projects and talked to several users that have the same issue. I have contacted Atlassian Support directly.