Jack Brickey Expert

Glad to assist. So Request Types are associated to an Issuetypes at creation of the Request type (project settings > request types). You might find this article useful - what-are-request-types and the related ones which you will find links to.

there is a known issue that is being worked. you may wish to subscribe to status update - https://jira-software.status.atlassian.com/incidents/x5yqyntc3kys 

go for it....ask your question.

There is a known and active incident for Automations in Cloud - https://jira-software.status.atlassian.com/incidents/x5yqyntc3kys 

great write up. i hate that you had to spend so much time on it. :-( There is a known and active incident for Automations in Cloud - https://jira-software.status.atlassian.com/incidents/x5yqyntc3kys 

I would suggest you look at the 2-Dimensional chart. I offered a similar solution just this week on another post. It goes something like this... * create a custom field called say MOY (month of year) w/ values of Jan, Feb, Mar... * using automation when issues are resolved update the field with the current month * use the…

Hi Candy, I am going to say "no" but TBH I need you to clarify what you mean exactly by "...Jira transition new issue...". If you mean to say "If an Agent transitions an issue created by a Customer will it affect the underlying data and if so how. Additionally, will it impact the portal layout?". So certainly when an issue…

be sure the admin or agent uses the "Raise a request" link in the sidebar and when they do they need to change the "on behalf of" to reflect the desired Customer. If they are set on using Create be sure they: * choose the correct issuetype * change the reporter * select the appropriate Customer request type

There is a known and active Atlassian reported issues w/ Automations - https://jira-software.status.atlassian.com/incidents/x5yqyntc3kys :-(

There is a known and active Atlassian reported issues w/ Automations - https://jira-software.status.atlassian.com/incidents/x5yqyntc3kys 

well > 4h is a Project Managers Dream! That will tell you which issues will be update in the future 4 hours from now and beyond.

@Harry Rombach each instance requires a separate user license. Licenses aren't per user globally where they can log into any instance. One thing I did want to make clear here is that I do not work for Atlassian. I am a user like yourself.

can you go to project settings > workflows and edit the workflow associated w/ your issuetype. click on the transition that you are attempting to do and check for any Conditions that restricts the transition.

do you have any organizations if so please check in them for the missing customers. also go to project settings > people and look there. finally go to admin (COG) > user management > jira service management and check there.

cool. I have been in the SLA abyss on a new project, whittling down 50 goals to 20. I had to create a spreadsheet to analyze the 3D data. ;-)

So I assume that you or your team are falling into a assignee, reporter or watcher for any of these issues. According to notification image attached, those are the only individuals that would receive a notification. And as you had mentioned earlier anyone will not see notifications for updates that they personally make. 

Hi Timothy, if you are an admin check the associated project settings > notifications and see if the settings there explain why this is happening. I assume that some admin has set it up to notifiy a group/role that you are associated with for the various updates.

I thought I would add a tip I just learned.... Use "No-one" in a rotation to 'skip' time periods. I was scratching my head on how to have someone on-call every-other weekend. By including "no-one" in the Participants field of a rotation you can make that happen... Jack --> No-one --> Jack --> No-one...

well if I understand your goal....sure. How you do that depends on what field is use to differentiate the stories w/in the epic. For example, using your labels approach... "epic link" = my-epic and labels = label1 or "epic link" = my-epic and labels in (label1, label3) of course you don't have to use labels.... "epic link"…

You should simply install JSM into your current JSW instance. Simplemente debe instalar JSM en su instancia JSW actual.

so in Excel I can simply enter the JQL w/o the need to select project....

@Milan Mainassy , i don't know what "epic-link code" is. and epic link is just a link associated w/ a given epic and it can be used in underlying stories/tasks to associate them w/ the epic. Please explain your use case in detail. 

this is not possible. only the last column is consider Done for scrum

yes. an epic is no different than any other issuetype where issuekey is concerned.

yep. I didn't suggest that as I was unsure if you would ever have more than one sub-task. Generally speaking, when using sub-tasks you have more than one. Sort of like a bulleted list. 

what do you mean by different "code". If you mean to say you wish to have a different issue key prefix, e.g. instead of ABC-123 you want DEF-123, then no. The issue key is a combination of project key and a sequential number of all issuetypes in the project.

There are two scenarios: moving all data from one instance to a new (empty) instance or merging two instances.... * Moving - simply perform a full backup and then use that backup to restore to another new instance * Merging - follow these instructions - merge-multiple-instances-of-jira-cloud Other articles:…

consider adding a label or a comment to the issue when it moves from B>C the first time. couple this with an extra condition, e.g. label != "already-happened".

Yes. You can reach out to Atlassian Support and they should increase for you. I did. However, I would also carefully inspect your SLA needs. Often times things can be combined into fewer rules.

you might also consider an addon app. there are a few in the Marketplace for customer feedback.