Comments
-
While you could simply use the built in Widget for 1 & 2 in order to achieve 3 you will need to develop this. Here is the developer reference - integrating-with-jira-cloud
-
Yep that will be the culprit I expect.
-
To be clear you can give an agent “project admin” rights and they can create queues. This does not give the full Jira admin rights.
-
It depends on what you are actually trying to do. There is a single source for layouts under project settings > layouts or when looking at an issue in the new view there is a “configure “ link to get you there. Now, layouts are associated with workflows and screens. If you define unique workflows by Issuetype then you can…
-
Wish I could help. :-(
-
As you are using server then you will be using your own mail server vs cloud where you could be using their hosted mail server. As such you can work with your IT group to get reports from the mail server. I don’t believe there is a way in Jira itself but am not 100% sure about server.
-
AFAIK, that isn’t supported, yet anyway. I don’t use it much as my role requires things that aren’t supported. Primarily admin functions.
-
Check the notifications of the specific project not your personal settings. You should be in a role, e.g. service desk team and that role needs to be associated with the desired notifications.
-
@sgroazil , this thread speaks precisely to your question. You don’t move the original issue to the JSW project as it breaks the connection with the customer. Rather you create a linked issue and if desired add automation such that the JSD issue is updated based upon the transitions of the JSW issue. Yes you end up with…
-
The customer origin is a custom field. You can create a JQL query that will find all issues. For example project = abc and “customer origin” = yes or sprint in opensprints() and “customer origin” = yes
-
nope and IMO the portal could benefit w/ some major refactoring. A kick-ass portal would really go a long way toward taking JSD up a notch.
-
no....well maybe....well sorta-kinda. :-) So you certainly cannot add via bulk edit. It is intended to simply edit existing issues, not create issues. However, you could consider doing something creative by incorporating an automation addon like Automation for Jira, Scriptrunner, etc. It would go down something like…
-
consider this addon - canned-responses-pro-templates-for-jira
-
puede encontrar este hilo útil - Where-is-Jira-Service-Desk-spanish-documentation-online
-
This is a larger topic that will be difficult for me to answer in this forum. Here is what I can offer: * Consider the use of Dashboard gadgets * Review the articles here particularly this one * Play with the many options to better understand and formulate your requirements and what works best for you and your team
-
There was a reported incident but was show to be fixed.
-
note: as a customer they will only get public comments. given it is the agent's manager you may wish them to be able to access the issue w/in JSD app (not portal only) and see internal comments, additional fields, etc. Just depends on your requirements.
-
Yes. if they get a notification and click on the link it will open the issue in JSD and they can view all aspects of the issue. Note this assumes that the individual has been setup in a role/group that has browse permissions. If you want them to be able to comment (internally only) then give the role/group comment…
-
here is one - JSDCLOUD-4580 and you will see related ones linked there. You can vote/watch if you like.
-
thanks for the insight. i have used a number of the "g" shortcuts. I guess g-p makes for sense for project. I see "a" as "assign" when viewing issues.
-
this is not currently possible. while you can display them in the detail issue view you cannot configure the table/list.
-
I have never seen any way of accomplishing this. I checked JAC for possible suggestions but didn't immediately find any.
-
so i suspect you are using a next-gen project. can you confirm? Assuming so you cannot achieve your goal.
-
BTW, you can find existing reported issues here - https://jira.atlassian.com/secure/Dashboard.jspa
-
i have never used the "g a" shortcut. not even sure of its purpose TBH. In any case I tried and indeed the sidebar is ghosted w/ placeholders. report bug here - https://support.atlassian.com/contact/#/
-
this is not possible. agents must be licensed w/in the instance where the project exists. But w/ cloud you can always add them and then later remove so if this is a short term gig then it shouldn't be a big financial impact. Otherwise consider using an addon e.g. automation for Jira (which will be integrated into cloud…
-
If you are saying you want to find all open bugs at the end of the month then I suggest you set up a subscription that runs monthly. issuetype in (bug, sub-bug) and status not in (closed, done) If you are wanting to find issues that were opened during the current month and not closed in the current month, I would again use…
-
I would check with your Jira Site admin to assess what has changed since yesterday. Based upon what you have conveyed and assuming there are no missing pieces I would guess they have made some changes that resulted in this issue. For further support from the Community we would need more info. Which fields can’t be edited?…
-
You can either use the Ranking feature or if you wish to use priorities you can either edit the filter to include “...order by Priority desc” or you can create swimlanes by priority.
-
Assuming Joe’s manager is a user in Jira either add him/her as a Watcher (they will receive notifications per Notifications configuration). if they are not a user in Jira then you would need an addon, e.g. Automation for Jira or similar. The nice thing about A4J in Cloud is that it will soon be integrated.