Jack Brickey Expert

Hi @Ayman Al Hakim , Welcome to the community. You cannot send Commands via email the only thing you can do is create tickets and add comments to tickets. 

Can you go to Project settings > email requests > and View logs? What do you observe?

@Cameron Taylor , I believe where things ended up is 1000 (premium) for Global rules and unlimited for project rules. this article might be useful - how-is-my-usage-calculated 

I'm just a user like you so I can't contact the person in charge. Do you have a ticket number that you received back from support?

I really like the look of that Kaiserschmarrn! And totally agree do not ruin that beautiful dish w/ raisins!!! I live in Sanford NC (small town outside of the Triangle (Raleigh, Durham, Chapel Hill). Favorite food: man I love all food it seems, well almost. I love seafood: oysters, clams, grilled fish. I love BBQ and love…

so here is where this is getting done. You need to edit the workflow. click on the transition(s) into the done(?) status click on the Configure under "show transition in the customer portal" and choose the desired resolution in the pop up. I highly recommend you undo what you did w/ "Resolved by customer" since resolutions…

So I think you are saying that you have a rule that references a Epic Link and each month you create a new epic and need that original rule to be updated w/ the new Epic Link. So basically one rule invoking another rule. Here is a previous thread where this was discussed. Ultimately what I think you want is for the…

yep it has indeed changed and Move is the ticket! :-)

Hay una versión gratuita de Jira que tiene algunas limitaciones, como hasta 10 usuarios y faltan algunas características. Esta versión se puede usar gratis para siempre. O hasta que Atlassian decida no continuar con el plan gratuito. :-)

if you are on Server, to the best of my knowledge, the "Create linked issue" doesn't exist but I don't use server so cannot confirm. If you are seeing that option then great. If not, then you can still create an issue and link the two using "relates to", "blocks", as examples. If you are not seeing the JSW project in the…

Hi @Сахаревич Янина , welcome to the Community. I'm not sure what your goal is here. It sounds like you have a rule to create an epic each month and this is working correct? Now you are inquiring about how to put a link on the epic? This is the part I don't understand. Are you trying to add an issue and link it to this…

did the "customer support" link resolve to where you reported the issue and if so did you get an email back acknowledging receipt of your request? If so then they will get back to you at some point I suspect. In the email you can click on the link to the issue and escalate. If you did not get an email acknowledgement let…

it needs to be in the right-most. adding multiple done will give the user the ability to drag-drop into each 'done' status separately. Alternatively, you can exclude "Rejected" status from your board's filter altogether but when the person drops into the column that maps to Rejected the issue will disappear.

if you are saying you have a JSD issue that requires the Software team to address and the Software team is currently using JSW then yes, you should create an issue in the appropriate JSW project and link the two issues. You should not "move" the issue to JSW (IMO). In JSD you need to be an agent or admin in JSW project you…

if you can access the previous instance and you update the billing info then it should be restored. If you try the URL and it is not accessible please reach out to Atlassian Support

once you move them you can edit each and add the epic link to them. if there are only a handful you can do this one at a time. if there are many consider the following: old project: * run a query/search to return all of the issues you want to move * use bulk change (ellipses in top right of search results) * choose all of…

Hi Aleksey, can you please confirm that your "green statuses" (done category) are in the right-most column and also the Resolution field is set. If this is not the case the issues are not consider complete and will return to the backlog/next sprint.

You can use the Move feature (maybe). You need to have permissions to do so. When viewing an issue click on the ellipses in the top right and see if you have Move option.

So I thought that you could achieve this by setting the jira.issue.editable false property on the Done status since supposedly adding issues to an epic is controlled by the edit permission. However, I just spent a few moments trying this but it did not work. A bit perplexed by this TBH. There may be a way to do this using…

ah yes! my bad entirely. I also just noted you are on server so forget all that Next-gen stuff. :-) I have not had the need to leverage issue level security feature as yet but indeed it should meet your needs. I found this thread and the post by "Ro" to be particularly detailed. It doesn't look to difficult to set up but…

Hi Anish, if you are using Classic and not Next-gen projects then you can use a Condition on any transition that only allow Assignee or a group, etc to perform a transition. However, you can’t prevent a member of a project to view only their issues. permissions are at the project level not issue level.

Can you check automations? The key is to determine where “won’t do” is being set. So if the agent resolves how is resolution set, via the resolve screen? Is resolution required a close via a Validator on the transition?

Hi Dave you need to create an automation to execute the reopen transition when the customer comments on an issue that is in the closed status. You can also choose to notify all agents upon reopen if that is required.

You can use Field value changed as the trigger and select the Request Participant field. That may or many not meet your needs.

Thanks Andy! Yes indeed that does need to be configured for Widget to work. I think that info is illustrated when setting up the widget if I recall.

there is no "one" source. Actually, i'm in the process of trying to write an article on automation and plan to add some basic examples and was going to leverage it to implore others to add their favorites, but just can't find the time of late. Now, there are sample rules in the app by default. Assume you have seen those…

well you will need to be an admin of the project which I'm guessing you are not. Go to the JSW project > project settings > permissions. If you are not an admin of the project find them and request their support.

Yes Automation was the original method for performing automated tasks inside JSD. Project Automation is the new kid on the block. For now they remain separate but I suspect they will be combined into a single solution. I suspect, but do not know, that any unique and useful automations available inside of Automation (like…

check this article that reference the UPM to be able to manage addons from w/in the app - universal-plugin-manager-documentation 

@Marta Solohub, make sure you have permissions to at least browse the JSW project in question.