Jack Brickey Expert

Elena that was in my earlier post.

If by "access" you mean the ability to be assigned/work issues you would need to make them an agent. If you only want them to be able to browse then if that person happens to be a Jira user (software/core) then you could give them browse access.

if you manually transition an issue to IP can you set the Assignee? The log seems to not like your attempt to see assignee. I might try something simple - replace the action w/ maybe a comment just to see if that works. I suspect it will and there is something about your transition action that is invalid. Note I don't use…

Hi Karl, welcome to the Community. I would refer you to using a Dashboard where you can present data via various gadgets. Here is a good read on this - what-is-a-jira-dashboard For example if you want to 'measure' # of tickets by reporter you might choose a pie chart or maybe a 2-dimensional chart. Let me know if this…

Salut Lina, bienvenue dans la communauté. D'après votre message, je ne peux pas vraiment dire pour quoi vous avez besoin d'aide. Il semble que vous essayez de soutenir un projet de support pour un client. Est-ce le cas? Avez-vous envisagé JSM plutôt que Jira? Pouvez-vous fournir plus de détails sur les domaines dans…

what about Created vs. Resolved gadget? If not then simply create a filter that presents the results and choose maybe the Calendar gadget?

to be clear the Resolution field is indeed quite useful to qualify any "done category" status. However, the point of issues being considered complete in a sprint but being put back into the backlog/next sprint has to do with ensuring the issue appears in the right-most column of your scrum board; unrelated to Resolution.…

so let's see if I can articulate the desired SLA behavior you want. Start SLA when issue transitions from Needs Approval to Waiting for Support. You don't want to start on Waiting for Support if the issue doesn't go thru Needs Approval. Is this correct? If so, given the limited conditions available to us for SLAs, I might…

Two methods of using Classic project. * Transition - edit workflow and on the specific transition you can add a screen that pops up to display the field. Also add a Validaor on the transition require the field. You could do this using a post function but I assume that you want the user to select the option. * at Create -…

You can use Automation. Have you attempted this? Here is a link to the docs around working with date fields to assist - smart-values-date-and-time-functions 

Both statuses must be in the Right most column of you scrum board. I suspect Resolved is just to the left of Done column? Only the RM column is considered done from an agile process in Jira. 

Maybe replace enters “waiting for support” with issue created? I would need to see more details to recommend definitively. The key here is that you don’t want to start SLA if the issue “reenters” a status it seems. 

Unsure TBH. I haven’t run into this but haven’t tried this specific app. Recommend contacting Atlassian Support directly. 

In a word No. there are a number of posts in the Community on this question and for more details I would refer you to the search box here to research the issues and challenges. For starters - https://community.atlassian.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&q=Shared+mailbox 

You deleted your Atlassian account or you deleted your user from your instance? The fact that you are posting here tells me you have an Atlassian account but maybe you have multiple? If your user was deleted from you Jira instance it cannot be recoveryshort of restoring from backup.

What does Automation rule logs convey? Documentation reference - automation-triggers 

Not sure I understand but you seem to be saying that the number “2” at the end of two statuses, e.g. In Review2 and Closed2. Is this the case. If so then I would say an admin made a poor decision on naming of statuses. They saw that In Review and Closed were existing statuses and they didn’t want to use them for some…

If I understand your requirements you should simply create a custom field single select with Yes and No as the options. I assume you will want to require the field to be updated maybe at create or as a transition as well. You may wish to set a default value (No?). 

Did you try to go to the Marketplace and download from there and then install?

Queues display only what you configured them to display. If you only wand issues assigned to say Fred then incorporate that into the JQL that defines the queue, e.g. assignee = Fred 

You would need to open up as Support and Request with Atlassian Support for this request. 

Yes absolutely! The portal is indeed the answer when structure is important. 

you cannot. If you were on Standard or greater you could reach out to Atlassian Support and they could assist w/ this but official support isn't available to Free instances.

you could achieve this using Automation by parsing the email. However, the reliability of that might be a bit questionable as it relies on the user following proper formatting. So you would end up having the automation do the best it could and then any that were not deterministic would fall into Unassigned/Triage queue.

you can hide the sidebar but not sure that is your goal.

Hey Renato, so your instance looks a bit different than mine but I believe that is because you are using the new JSM which includes Opsgenie capabilities. In any event AFAIK you cannot modify the sidebar to remove items. With that said, cloud is changing frequently. You might wish to provide feedback to Atlassian on your…

Hi Wim, disclaimer - I use cloud so I can't give you specifics on Server but hope this doc might help - managing-service-project-notifications 

there isn't enough info to give you a full (?) answer but here are my thoughts... Trigger: issue created Conditions: whatever meets your needs to zero in on the need to take action Action: you if/else blocks and inspect the values in the multi-select and set the components accordingly One question I have is why do you need…

please provide a screenshot of your automation. Also, what does the automation log tell you? I have found the logs to be quite helpful when debugging rules. 

you don't choose "Issue fields condition". when you click on Condition type in JQL and the option should be there.