Jack Brickey Expert

i expect we can. but need to know what you have and what you want. If you are simply wanting to change the progression of your workflow between the statuses then you need to edit the workflow and simply drag the transition around. depending on the details I would likely suggest that you make a copy, edit the copy and then…

As I recall there is meta data in the header that JSD uses as well to determine new vs. existing. You either need to make the "third party" a customer and participant and use JSD to communicate w/ them or you need to remove the JSD email when forwarding.

what many of us do for Kanban is to add a filter to age out the Done and we use the Sub-filter for it. resolved >= -1w OR resolved IS EMPTY

to the best of my knowledge. I haven't used server in a few years but I don't expect it has been added. I have seen similar posts in the Community that I believe confirms that. However, I cannot say this definitively. Atlassian closely controls the layout of screens into areas. 

not to "releases" but you can add date fields to "issues" and those issues are associated w/ "releases". Then you can create a view, e.g. a filter, dashboard, etc. that display the dates. Given they would be at the issue level it would be a pain to set them manually so I would investigate how to automate based off the…

ah reflection... better than reading email! Jack's career (what he can recall)... Job ==> Lessons * cutting grass in the Southeastern US ==> ticks are hard to remove so get them off early * delivering papers ==> at Christmas time you sometimes get a bonus from your subscribers. yay new toys! * packing albums & 45s (yes i'm…

 There is no capability of doing that in the cloud. You might check for add-ons to see if there something in the marketplace for that 

Sure. You simply need to ensure the customers only have permissions to the specific space. You might want to start with this article

You can “link” stories and tasks using the Jira Link function. You will have to do that within Jira not Confluence. However, you can’t associate tasks to stories in the manner that stories/tasks are associated to epics. You can have sub-tasks associated to stories in that manner.

I have never experienced this but don’t know that I have ever attached different files with same name either. I would suggest you reach out to Atlassian Support on this issue.

Is this the case with any Customer or a certain customer? Can the customer create a ticket via portal? I would first check the portal to determine if it is a customer permissions issue or an email channel issue. You can check to ensure the customer is indeed listed as a customer for the specific project. Test if anyone can…

Likely yes. You can test it easy enough by removing that.

You can certainly create multiple orgs. You can have multiple orgs per Project or associated with separate projects. If in the same project your customers will see the same project portal but cannot share outside of their org.

I assume you are attempting from Marketplace? Have you attempted to install directly from within your instance (under settings) rather than the Marketplace?

are you talking about via the browser or the app? I can certainly do so via browser. The app is a bit more limited in this regard. Have you attempted and are having issues?

Try this project = dkadc and issuetype = story and resolutiondate >= -14d

Agree that automation would be wise. I use Automation for Jira as Cody mentioned and it is quite powerful. If your requirements are such that it results in less than 300 per month the you can go with free. I recommend you install the free version and play with it and get a feel for it. Their documentation is quit good too…

You can often find answers by using the search bar at the top of this page. Here is one such article- Reopen-ticket-with-automation-rule

JD, there really is a good bit of detail missing that makes it hard to give you the 'best' answer but I will try and frame it up w/ the assumptions and conditions that are in my head. If i had an image of your current WF and a bit more details. Again this all depends on how you want to solve it and my answer is how I would…

Hi Tim! You need to edit the workflow associated w/ the issuetype. Select the transition you are interested in and add a Screen to the transition that will expose the desired fields. If you don't already have a screen you can choose from you would then create one before editing the WF.

@Bob Taylor , please have a look at this document if you have not already done so. receiving-requests-by-email. If you are on Server be sure to click Server/version in the top right of that article.

Hi Teresa and welcome to the Community. The easiest way is to look w/in the project > reports screen itself. The choices are listed there. They differ depending on the project. You can also look in the Atlassian documentation: * setting-up-service-desk-reports * jira-software-reporting

Here is a suggestion to try... * create a user picker custom field called "Escalated by" and have the escalator set to their name when they escalate. you could consider automating this, copying the current assignee in but if they change the assignee before escalation then that would fail. something to investigate. * use a…

Adam, yes I would agree that would be nice for sure. Of course that could be said for a number of scenarios, e.g. addons, etc. Unfortunately, the licensing model is based on total user. You might want to provide this feedback to Atlassian via the feedback link in your instance.

wow! that is impressive for sure!

that definitely isn't one of my powers but sure wish it were. i love to read but it takes me forever.

LOL!!! you definitely when here and am reserving a spot for you in my re-Avengers team!

@Manuel , it sounds like your board's filter that is used to define the board isn't aligned to the workflow changes you made. I can't tell you precisely what to change as I don't know your previous WF or current one. With that said, please look at the current board filter and simply try to edit it along w/ the columns in…

you can convert the sub-task to an issue and then do what you want with it, mark Done or work as an independent task/issue. As Joseph said, deleting an issue is not a great idea. I won't say never but unless there is a real compelling reason and care/thought is given then don't.

I you mean project type, you cannot create your own but you can change (unless you are trying to change a NG project). Note there appears to have been a recent change in Cloud. Whereas you used to be able to change by going to project > project settings > details and changing Project category, i'm not seeing instructions…