-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
4
-
When creating an issue from within an epic the creation screen defaults to the last project whether it matches the epic or not. Customers would like this to default to the parent project of the epic.
- is related to
-
- Gathering Interest
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-8867] Default the project for a new issue to the project of the Epic it is created within
Mani
added a comment - +1 from Bloomberg. Happens to me everyday and sometimes it defaults to a project I don't have access to so I can't even move it or withdraw or delete it. Then I have to create a new issue and another team is left with a random issue in their project 
Mani
added a comment - +1 from Bloomberg. Happens to me everyday and sometimes it defaults to a project I don't have access to so I can't even move it or withdraw or delete it. Then I have to create a new issue and another team is left with a random issue in their project 
Paul Gambill
added a comment - A thousand +1s to Laszlo's comment. Is there a separate issue tracking that feature pobara? Several times a week I create a ticket while viewing one board, only to find out that it went to a different project that was selected. I understand the need to have the project drop down, but I want the default to be contextually accurate to whatever board I'm looking at at the moment.
Paul Gambill
added a comment - A thousand +1s to Laszlo's comment. Is there a separate issue tracking that feature pobara ? Several times a week I create a ticket while viewing one board, only to find out that it went to a different project that was selected. I understand the need to have the project drop down, but I want the default to be contextually accurate to whatever board I'm looking at at the moment. 
Laszlo Kremer
added a comment - +1 (plus a dozen votes from our userbase 
.
It happens with users that they are actually editing an issue in project A in an other window and then they click this button on their own board (project B), and they accidentally create a ticket in project A.
Can be confusing, where the new ticket went.
Laszlo Kremer
added a comment - +1 (plus a dozen votes from our userbase .
It happens with users that they are actually editing an issue in project A in an other window and then they click this button on their own board (project B), and they accidentally create a ticket in project A.
Can be confusing, where the new ticket went. It is by design that we allow issues from multiple projects to be organized under one Epic. Therefore, this is not a bug but we will consider an improvement to the default project selection.
2 things here:
1. Giving the users the option to change the project for the issue leaves a risk that the issue can be created under the wrong project
2. If you are adding issues to multiple projects in the work board, the project drop down is often defaulted to the wrong project.
To me, it makes the most sense to remove the "Project" option completely if a user tries to add an issue to an epic from the planning screen by clicking "Create issue in epic". If this is not possible, then the next best thing would be to change the default value of the project to the project that the issue is under.
+1
We use a project per customer.
My dev's workflow was: open the Jira board for the project we use for customer B. Open the epics tab. Click create in epic (an epic that only applies to customer B). Oops, it defaults to the project for customer A.
This causes a risk of leaking information between our customers.
If you're looking at a particular board it when you click a create link, the project should relate to that board's filter (in my case, that board's filter has project = B).