New issue procedure

[David Lagewaard]

How can I set my preferences so that when I have created a new issue, the new issue opens without me having to click on the notification that a new issue has been created.

Presently it is a two step process.

1. Post the issue

2. Click on said notification to open the new issue

An that is quite illogical since afetr creating an issue it is the most likely that the creator wants to continue with that new issue. Like adding attachements ertc. etc.

[David Lagewaard]

I do not exactly understand why, but I am supposed to  view and accept you answer and to mark it as an accepted solution.

However, when I log in I do not see how I could do this.

Apart from this. I appreciate your answer, but it doesn't help me very much, does it?

Perhaps the people of Atlassian follow what is going on on this platform. If they do they might come up with a response.

[PeterN]

Strange...since I did not want to give a "full" answer, only my approach toward the same thing. Let's see, if someone has a better idea.

Thanks!

[Nic Brough -Adaptavist-]

There is a grey tick to the left of every answer.  Click that to mark it answered.

Atlassian are active here, but they don't often take conversations here as requests, and when they do, they raise them in JaC as suggestions.  You can do that as well - go to https://support.atlassian.com/contact to be routed to the right place.

However, as the move to "create and tell user they've created while staying in the place they were working before" is already a result of a suggestion to do so, removing it is unlikely to happen.

[PeterN]

Hello David,

with the same "two step" logic in mind, I added more fields to the "create issue" screen, so it would pretty much allow me all neccessary inputs (custom fields etc.).

I am looking forward to more input from other users, which found a better solution.

Peter

[David Lagewaard]

I did something  similar, but it is  not a solution.

The way the matter is approached is far from intuitive. A user who created an issue will most likely continue working on or with that new issue.

[PeterN]

Agreed...I am looking forward to other approaches.