I have the following structure of their clients with projects associated with them:
1) Client A
--- Project A1
--- Project A2
2) Client B
--- Project B1
--- Project B2

When I try to add a new ticket (node/add/support-ticket) the form always brings the default client (A) and its two projects (A1 and A2).
Even if I switch to client B, the two projects remain A1 and A2.

How can this be solved?

CommentFileSizeAuthor
#2 projects.jpg18.48 KBrogeriodec
#2 tkt1.jpg28.21 KBrogeriodec
#2 tkt2.jpg32.92 KBrogeriodec
#2 tkt3.jpg29.27 KBrogeriodec

Comments

jeremy’s picture

jeremy commented
Category: bug » support

I'm unable to duplicate. Configuration happens at admin/support/project. Perhaps upload a screenshot of your current configuration?

Per your description above, you should have a list of four projects. Project A1 and Project A2 should be assigned to Client A only. Project B1 and Project B2 should be assigned to Client B only.

rogeriodec’s picture

rogeriodec commented
StatusFileSize
new tkt3.jpg29.27 KB
new tkt2.jpg32.92 KB
new tkt1.jpg28.21 KB
new projects.jpg18.48 KB

In projects.jpg you see some projects and 2 clients.
In tkt*.jpg you see these 2 clients but an empty Project drop-down list.
This is because it is not given a refresh when changing the client.
But I see no solution to this using the standard controls of drupal.
The only solution I see would be to add an argument in the URL by entering the client to bring the list of projects associated with this client.

jeremy’s picture

jeremy commented
Category: support » feature

Ah, I see your issue. Currently the module doesn't auto-update affected selectors if you change the client while creating (or updating) a ticket. Currently the only work around is to first navigate to the correct client queue before creating the ticket.

For example, a related issue:
#436726: Make it possible to assign ticket to other user at ticket creation

purencool’s picture

purencool commented
Issue summary: View changes
Status: Active » Closed (outdated)