Comments
-
Yes. You can use the request-channel-type in a JQL and you can also use this in various Gadgets in a dashboard.
-
My suspicion is that the statuses the issues are in are not reflected in the board. However it also appears you are using a NExt-gen project. What status are the issues in? Are these statuses reflected on the board?
-
That is good info Stephen and I want to dig into this more to understand if Access is in fact not required which would be really nice. My understanding has historically been it was required. Fingers crossed.
-
My understanding is that for Cloud you would need to incorporate Atlassian Access. Here is an old issue that was recently updated that discusses the various integrations with user management. https://jira.atlassian.com/browse/ID-79
-
Consider this... you could have these issues as different request types and hide the RT from the portal. Your agents could create the tickets and add the customer(s) as Request Participants.
-
have you inspected the rule logs? Compare a run that succeeded with one that failed. Also, I recommend using the Action log event to record data about the run so that you can interrogate the log more completely so you are guessing at what the values are that are being compared in a condition.
-
If you are on Cloud there is no opportunity to modify this. If on server I would assume you could crack open the code and modify. Not that I would recommend that.
-
It appears you experienced an unhandled exception in the Jira desktop or mobile app? If this persists I would reach out to Atlassian Support. In the meantime use the browser version
-
NG is a ground up development so it wasn’t removed. The relationship between Epic and its children is simply different.
-
That looks correct but TBH I rarely use the gadget. There isn’t a mouse over solution OOTB.
-
I would suggest reach out to support directly as this seems like a bug. I’m on cloud so unable to test.
-
Mark, something is definitely amiss. As you stated, and you image shows you have no request types listed. Are you sure you are looking at the same project and group?
-
Well it is personal preference but when I use “story” I do follow “as a xxx user” but if I use “task” I am less strict.
-
Odd for sure. I assume if you manually transition the date is set?
-
Have you looked at the Text gadget?
-
If you go to project settings > people what role(s) is she in?
-
If you are setting the Resolution then there should be a resolution date. Check to ensure the resolution is in fact being set.
-
Is this you app? status-time-support if so definitely reach out to the, on this issue and update here if you find the solution.
-
Hi Midhun, NG doesn’t support Epic Name.
-
Hi Ikem, yes this would be possible using Automation. Give the following guidelines a try... Trigger - issue created Conditions - JQL - reporter is memberof(“group”) action - edit issue > labels = “tech-support”
-
Only site admin can change the priorities. So if you are the only one then there shouldn’t be a concern unless you forget not to chang it.
-
It can only be changed by system admins so it comes down to agreeing on system level changes among those individuals.
-
Hi Erick, welcome to the Community. Unfortunately not. :-( Priorities are global.
-
yes saw that but at first blush it looks alright. did the logs indicate that did not pass the condition?
-
I think that will be the default value set for the Creative brief custom field. Assuming you have the necessary permissions... click on the COG > Issues > Custom fields, search for that field, click on the ellipses and select Context... On that page you should see the text as the Default value.
-
well it is better for me but that doesn't necessary mean it is for you. ;-) In the default (?) workflows there is generally a Respond to customer transition in the workflow. Basically, in new issue view the Agent simply selects W4C which invokes the transition. But ultimately it all comes down to your exact workflow. I…
-
Hi Laura, TBH I don't know the answer to this but have pinged one of the Atlassian Community Team members for an official answer. I agree that there should be a way to opt out. I have not seen many request for this (2-3) in my lifetime here but still a valid question to be sure. I will update here once I hear back. One…
-
Rob, i wonder if this is the proper procedure. You indicate "if a agent asks the customer for additional information or a question" however, making a public comment does not necessarily equate to a NMI or question to the customer. Sometimes an agent may be making a statement "all if going well just wanted to update…
-
well i use cloud so it is a bit different but here you go... Pre-requisite: you need to be an admin * go to Project settings in you project * go to Workflows * edit the workflow associated w/ you issuetype (in the event you have more than one workflow) * in diagram mode select the transition out of your 'done' status…
-
whenever you reopen an issue you should clear the Resolution field. This can be done via a Post Function (Update Field Value) on any 'reopen' transitions.