Jack Brickey Expert

We use Jira Service Desk for all IT issues. JSD provides a "widget" that is java-script embedded into any webpage. The user can simply click on a help button, select a request type to create and add their email. This doesn't exist in JSW however, so you might check the Marketplace for alternate solution.

I would consider an addon like Automation for Jira. Using this you can conditionally (if unassigned) set it to the reporter. The thing I like about this addon is the flexibility to do so many more automation tasks. Two other great options are Scriptrunner and Power Scripts (swiss army knives for Jira).

@Joao Soares , welcome to the community! We will need more info to assist I think. Here are some random thoughts that might assist you and convey the info I would need. How have you set up the incoming email handler? Are some project email handlers working? If so, have you looked closely at the differences between the mail…

Hi @Yossi Harel , given you are on cloud, if this is continuing I would reach out to Atlassian Support. I would also check different browser just to be sure there isn't something weird there but I doubt it. Are others experiencing this? Do you not have this issue when creating other issue types? I assume your connection…

Just my thoughts here. Ultimately the best way is the one that works for all/most of your teams. * If the dev team actually is the support team, which often is the case, then I would definitely use a single project. * If the support team is separate then I either would certainly work but I generally like to avoid project…

you can map Cancelled to the far right column to have those issues removed from backlog.

Within Jira, sprints are associated w/ a Scrum board not a specific project. You can create a scrum board using a JQL filter that references multiple projects if desired. The one thing you will want to take care with is to not overlap your scrum boards. That is, lets say you want one scrum board that cover all issues in…

you might consider an addon, e.g. Structure or using Atlassian's Portfolio

hmmm, how confident are you that there are not actually created? if you use the following JQL and sort by issue key most recent are they not there? Are you sure you are looking at the same project? project = xxxx

for cloud I did not find an addon but you can have a look maybe there is a solution out there. I have never considered this before but see where it could be useful.

So unless you have created a custom issue type and named it "Sub Task" then that is not possible. "Sub-task" is a special issue type that can only be created from within a parent issue not via the "+" button. If you did create a custom "Sub Task" issuetype I would first recommend against doing so as it will become…

Hi Edgar and welcome to the Community. When you say a unique number do you mean something different than the issuekey itself? Every issue in Jira will be created w/ an issuekey that consists of the project key and a number starting at "1" and progressing from there. This issuekey is a link in Jira to the actual issue. I'm…

Hi Murielle and welcome to the Community. There is no way to do this OOTB. I found this one addon - Mentions & Watchers - that is available for Server/Datacenter but not Cloud.

I have not heard this and I too can’t see how this would work. I know that you can use the widget in Cloud to create an issue without login but that isn’t the same as going to the portal. I will research further with my Atlassian friends.

What do you mean by “accounted”? If you are using Cloud you can go to profile and click Manage account to get to your info. If you mean “user ID” that is your email.

It depends on what you mean by “users” in this context. If you mean “agents”, which is what I suspect, then you simple need to ensure that the role used to define your agents is setup in the Create/Resolve notification scheme.

The create issue in Cloud is the “+” symbol in the far left sidebar. If they are not seeing that then you should contact Atlassian Support. However, I would be very surprised. 

Hi Kiersti, if a filed is missing you should add it to the edit screen. However in the case of Remaining time I believe it is only available thru the Log Work function which, for the detailed issue view screen, is under the ellipses.

What I suggest is to create a filter for the members you want to include e.g. project = abc and assignee in (1,2,3) then create a dashboard and add the Created vs Resolved gadget and reference the saved filter. This isn’t a bar chart but I think it does a good job. 

Hi Brian, I hope I can shed some light here and offer some advice. The relationships of issuetype categories in Jira are as follows: * Epics can consist of Stories/Tasks * Stories and Tasks are equivalent (just a naming thing really) * Sub-tasks can be added to Stories/Tasks * Sub-tasks cannot be added to Epics When…

not OOTB. You would need an addon, e.g. enriched-profiles-for-jira-service-desk

there are different approaches that I could think of but my vote for the best would depend on me better understanding your process. Off the top of my head I would suggest using automation addon to create the 'next' task for the other department once the current task reaches some status in the workflow. Another thought is…

With a single instance you only have one help center background and brand. You can have unique logos on the two portals. You might check the Marketplace for capabilities of various portal customization addons. 

@David Thielen , this is a different question. Regardless, go to Jira settings > System and backup/restore. You need to be a Jira Admin

Dean, I’m mobile at the moment so am sharing a thread that I believe answers this. It discusses the opsbar property. While I have not played with this in a couple years this what I would try. In cloud there has been so many changes the behavior may now be different. Please post your results back here for me and others.…

The only way I know of would be to restore the backup to another instance and the copy the text or import the issue into the current instance. 

Because, depending on the details of the workflow, there may be some manual decision that must be made. Simple example - statuses. If you have an issue in say “pending” on on task but you don’t have pending on the other workflow what status should the issue be mapped to when changing the issue type and workflow? A human…

Done

Likely yes. You would have to use the Move feature to move an existing issue to “new feature”. You will then want to adjust the Request Type to one appropriate for new feature.

I don’t know of any commitment of when this might be released fo NG.