How can I configure the issues that show up in the customer portal? Currently the only issues that seem to appear there are those that are directly submitted by email from the customer.
However, there are other requests that come through other channels (e.g. meetings, phone calls, etc.) that we create ourselves in the tracker, but which we would like them to see and be able to comment on.
*However, we don't want them to be able to see ALL requests*
How can I configure JIRA (server) so that we have this functionality? Ideally it would be a workflow transition which sets a field so that the particular issues does or does not appear in customer portal.
Assuming we are talking about a 'Service Desk' type project, if you want an issue that has been created through JIRA channel to appear on customer portal, make sure its 'Request type' field is set to the corresponding customer request type that matches your issue type.
You can configure your customer request types in Project Settings -> Request Types.
To make all your issues display on portal you need to make sure that:
1) Each issue type within your project is mapped to its own customer request type in Project Settings -> Request Types
2) All issues have their respective 'Request type' field set to a matching customer request type depending on their issue type
Could you clarify what do you mean by "I need a way to set so that certain requests do and don't display"?
@Ivan Tovbin we only use one request type for everything - new feature. Some issues which have these appear in the portal and in our internal tracker.
What I mean, is that I want to be able to crate a ticket, and then click a button which decides whether or not it shows up in custoemr tracker or not.
Right now it seems that the only issues that appear are the ones that the client submits through email.
@Ivan Tovbin I thought that was the same as the Issue type. But I see that in the field configuration there is an option for issue type and customer request type.
So I should be using this customer request type field? It is locked and programmatically generated. So how can I set this? I am admin.
@Ivan Tovbin That's a good idea and I looked into it. However, I can't do it on issue creation as that takes away the option to set it on a per issue basis.
So I looked into the other statuses for the automation ruleThe organizations added and particpant added would be good, however, these aren't able to be set as easy post-transitions in JIRA. The other ones are too generic and wouldn't work for that reason. IF there was an option to set it to automate when the status changed to something specific then I may be able to work with that, but currently it is not customizable.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs