Comments
-
I have never used anything other than the users email address. That has always been successful for me.
-
I am reaching out to us and Atlassian colleagues as well. Please post any information you get back from Atlassian here and I will do the same. It may be by design I just don’t know exactly the reasoning.
-
Are you using your full email as defined in the user details?
-
Ah…I ran into this awhile back. This is an ITSM project and the raise a request does not exist there. I do not understand the logic of this TBH and need to discuss with some Atlassian’s to better understand if this is by design, and if so why, or some oversight that will be addressed.
-
It is in the sidebar of each JSM project. It directs the agent to the portal request screen where they can choose the request type and set the reporter to the appropriate customer if desired.
-
So are you a Jira admin? Did you select “move to trash” from the view all projects screen?
-
This is why you need to instruct the agents to use Raise a request rather than the create button.
-
If you mean you wish to find issues created via the portal then the following JQL should work for you. Project = xxx and request-channel-type = portal
-
Not OOTB. If you were using CMP then you can require a comment using a validator on the workflow transition. However if you’re just updating a field then you would have to construct a listener that would watch the date field and then present a modal for the comment. This would require an add-on such as scriptrunner or…
-
You don’t want to create another project and duplicate all those tickets. The good news is you don’t need to do that in order to get a good overview of all the projects. You can easily accomplish this by using either a dashboard or maybe I Kanban board. You might find this useful - what-is-a-jira-dashboard if you go the…
-
You seem to be asking about Cloud in which case you cannot self-host, as it is SAAS.
-
It may now indicate “automation” as the sender but I think you can influence that and specify the one who triggers.
-
I think that would be pretty tricky. And I certainly don’t know of any current solution that exists. You could consider using automation for the issue transitions to resolved. However, what would your conditions be? Would you want to create a knowledge base for every resolved ticket? I wouldn’t think so. Maybe consider a…
-
If this is specific to your desktop then I would contact your IT department. Are others experiencing this.
-
Native JSM does not support this. However Opsgenie does so if you have Premium you can leverage OG. Then there are addon app options.
-
Unless something has changed recently that is not possible. I would suggest using the Feedback link in the application and convey your Suggestion to Atlassian.
-
I suspect that these “notifications“ are coming from automation not from the standard event trigger. If it comes from the standard events then it will be the user that triggered the event. If it is automation, specifically legacy automation, then the rule is run as the creator of the rule unless otherwise specified. if you…
-
Two OOTB options: 1- You can do it in batches: * run your JQL * edit your issues (1000) and add a unique label as part of the edit (“BE-complete”) * re-run the JQL but add …”AND labels != “BE-complete” * repeat the edit operation including the label * repeat to end 2- you can use CSV import * there are a number of posts…
-
Cloud does not have release versions. As a sass product Atlassian is constantly rolling out new content. When versions are rolled out they come in waves to the various instances. So while I may have seen these changes three weeks ago those changes may have come to your instance say two weeks ago. If you want to keep up…
-
Then you need to contact your Jira admin
-
I am not where I can check at the moment. If you go to Jira.Atlassian.com you can use JQL to search.
-
Disclaimer: I do not use TMP and things change very quickly. With that said the last time I checked on TMP and the rules, estimation was not an available option and it appears that it still is not based on what you were conveying.
-
I’m sorry I don’t quite understand. So are you trying to access the user management page? If so you will need to have Jira administrator permissions. When you click on the cog icon in the upper right there should be a user management option for you.
-
Agreed that is why I almost always opt for a single done status and allow the resolution to specify the type of done i.e. it can be done-canceled. In this way they can drag the issue to the done column and the pop-up will require them to specify the resolution.
-
Sprints are independent and need to be manually planned and started.
-
e se você formar um JQL com o valor dos rótulos, ele não mostra resultados? se sim, entre em contato com o Suporte Atlassian.
-
You can create three text fields in your Jira service management project and expose that under the specific request type form.
-
então sua atualização recente me confundiu. Inicialmente estávamos falando sobre um campo chamado categorias, eu acho. No entanto, agora você está apontando para o campo denominado rótulos, que na verdade é um campo do sistema. Se você está tentando se livrar de um rótulo, a história é diferente. A única maneira de fazer…
-
When you’re looking at the issue screen you see status. What is displayed or not status categories they are simply statuses. Now one thing that I think is probably confusing you is it just so happens in the default project that you’ve created the statuses are exactly the same as the status category. In its simplest form…
-
Understand. My point to Mahima was that he would need an addon to achieve the goal. Scriptrunner is one such addon.