Jack Brickey Expert

Personally I like to create a dashboard that includes my “due soon” issues. I check my dashboard each morning. 

I expect this is a temporary issue. A few things to check. Try a different browser. Try logging out and back in. Ask for another admin if they can try.

Have you looked into using Automation? Here is one post that should give you a starting point. Sync-comments-between-Service-Management-and-Software you can tweak to meet your needs.

Have you had the individual check their spam/junk folders? one interesting test - Create a manual automation that has an email action to this individual. The trigger can be something like create issue with a special label condition. The goal here would be to see if she receives an email when the manual automation is…

While the workflow sure looks scary, I’m unsure what your question or goal actually is. I might start with getting rid of all (most?) of the loop-transitions in your workflow.

Based on what you have conveyed I would recommend using a Company Managed Project template so that you can leverage Conditions in your workflow. The Condition will be to allow/restrict users on Transitions.

If you enter the following JQL into the advanced search for issue screen does it present results? “Freshdesk support” is not empty

so bizarre. not sure I would have made the bug Low priority. I get that there is a work around but not a pretty one. :-(

when you refer to group/role are you talking about Agents or Customers? If your goal is to service the same customers for all requests (backend and HR) and you are trying to restrict what your agents see/work on them you could consider Issue Security schemes. Yes however your customer base will vary across these projects…

Best depends on your perspective. Are you looking for a tool that makes it easy to import or are you looking for a free OOTB solution? OOTB you can use the CSV Importer. if you want a tool look to the Marketplace, e.g. csv-user-importer-for-jira or import . Note I have no experience with either. Just offering options found…

When I export current fields I do receive the epic key for the Parent but not the epic name.

ah yes good point @Bill Sheboy . I had forgotten about this limit I had run into this once before and had to re-factor my automation to make it work. Ultimately I created two separate rules.

Unfortunately you cannot limit request types based on customers. All customers forgiven project will see the same request types offered. The only way to deal with this is to create different projects and give the appropriate customers access to the appropriate projects.

issue security schemes work on issue types not request types. More importantly issue security schemes will not apply to customers.

Hi Julia, welcome to the community. Upon archiving a project JQL will not return any results for said project. One of the goals of archiving projects and associated issues is to remove them from the various views completely. To the best of my knowledge there isn’t a means of querying archived issues.

that would do it. it is always good to start with interrogating the board filter first when something looks amiss on the board.

You can add conditions to your transitions to ensure hey Field has a specific value otherwise transitions are allowed. And you can add multiple conditions for multiple fields. However this is an "and" operation not in "or" operation. For example, if you have the following conditions * custom_field1 = x * custom_field2 = y…

Currently there is not the capability of providing granular permissions for Customers. All Customers have the ability to create issues. There is an open request that is similar to this for providing read/view only Customers. JSDCLOUD-8969 - Allow customers to share with read only permission to Other customers in their…

good find @Garrett McCreery 

yes. you can define the goals to exclude change requests. such as... ... and "request type" != "change request"...

I wonder if it is actually changing the due date on the first create issues step or if rather your change is not saving. My point is in your video you had now in the second step and then you edited and replaced it. And when you returned it went back to now. It appears that you did click save. On the surface it sure seems…

Hi @Esther Amunga , you can certainly create these issues in your JSM project and you can create unique SLA to track progress. I cannot share my thoughts on the approach without understanding more details. It might be that you simply create a unique Request type or maybe you would be best served with a unique Issuetype.…

Hi Evert, I am not following you here. Isn’t that precisely how it works? The create screen isn’t agent specific. What exactly are you experiencing that you wish to change?

You might find the answer from Alexis useful in this similar post - Automation-for-Jira-Clone-Epic-Story-and-Sub-tasks 

Duplicate post - https://community.atlassian.com/t5/Jira-questions/Configure-jira-email-notifications-to-users/qaq-p/1819753 

Duplicate post - https://community.atlassian.com/t5/Jira-questions/Configure-jira-email-notifications-to-users/qaq-p/1819753 

I will leave this to Alex as he is actively working it.

Can you provide more details. Specifically the queries you are using. Are any queries showing results? If you use these queries in an Advanced search for issues do you re eave results? Screenshot of board?

Hi David, welcome to the Community. Unfortunately you cannot relocate the field description location.

Yes you can do this. Creating 50 sub-tasks will be a bit of work but certainly doable. I would refer you to the for all the details but also use the search bar here in the Community for automation examples that may help as well. basically it will look like this… trigger - issue created conditions - specific conditions to…