nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue getting resolved with out asking the resolution

vishal03kadam

Hi All,

We have a few projects where this issue is observed. The projects are having Common Bug Screen Scheme where, when we resolve the issue a form get popped up where you have to fill the resolution. But we have observed that for some of the old issues when we resolve the issue it gets resolved without asking the resolution. Which is only happening for all the old bugs a newly created bug is asking for resolution before simply moving into the resolved state.

Now the question is why some old bugs are having this issue and how can I resolved this problem.

Thanks,

Accepted answers

All comments

Nic Brough -Adaptavist-

Have a look at the workflow for the old and new bugs - what transitions are in use for the "resolve" transition, what are the differences between them? Look specifically for the post-functions and screens in use on the two flows.

vishal03kadam

The workflow is the same for the new and old bugs, in fact it was never changed it the same from the project is created.

Nic Brough -Adaptavist-

So you are saying they are going through the same transition?

vishal03kadam

Yes

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-core