Peter DeWitt Community Champion

Christian, I have done this both ways. In one case we ran all the Atlassian DBs in single postgres instance and currently we run them all separately and local to the server. Both work without issue. -pd

Seethis discussion. https://community.atlassian.com/t5/Jira-questions/ParentEPic-in/qaq-p/647855 -pd

Huseyin, you could always set the reporter in a post function on the create transition. This would make sure it's set as the correct one. After that, make sure the field is not on the edit screen so it can't be changed.

Roberto, I'm not sure if there's a way to send out reminders that tag off the sprint dates but if you are using the due date field in the issues themselves (bulk update for all sprint issues) you could write a JQL query for issues due in x number of days and then subscribe the team to them. This way they would get a…

@Luis Krause, this sound like good feedback for the Source Tree guys. I'd open up an support request so it can be tracked and upvoted by others in the same situation.

Nice write-up Steven. I have also worked in systems with anywhere between 100 and 1600 custom fields. My rule of thumb is always: less is more.

Yes - as long as one of the issues in the internal part of the query has an epic link to it.

Are the dates in your subtasks in a specific field? Can you attach a screen shot?

Pankaj, Check the file size of the attachments. Maybe they are too big for what your instance is allowing?

Corey, I'd open up an issue with JIRA support. Since you have the new license purchased they should help you out.

Stephen, I do it manually with cloning the issues for the next month when I take care of the current set. I however only have a few task that reoccur. Like Nic above, the add-ons are overkill for the few I do.

Roberto try this: issuefunction in epicsOf('issuetype = story and assignee = yourname') This will get you all epics of any stories you are assigned too. issuefunction in epicsOf('issuetype = story and project = key') This one will pull all stories in a project and return their Epics. gl - peter

Brian, I'm not entirely sure what you mean by the two field in one column but you can show both field on a dashboard. Using the Filter Results gadget you can select both fields.

Alison, This may not be helpful. I missed that you are using Trello. I was thinking Agile in Jira... Alison, I think the best you will be able to do is restrict access. I do this with my template projects and boards in my instance. I restrict them to only the administrators group (or you could even restrict to just…

Alex, I run my Atlassian apps in this configuration. Check out these articles by Atlassian: https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html…

Anoja, from my experience the backup works as a single unit. It's all out and all in. I think you are going to have to migrate space by space. You could also looks at archiving / removing old content and pages. This would cut down on the size of the XML.

Srinivas, The most obvious question is Can you still get to the project without using the gadget or search? If so have you changed the name / key of the project? You may need to rebuild the index.

Rodrigo, it sounds like you're thinking about running in a Federated environment. Take a look at this Atlassian document for more information. https://confluence.atlassian.com/enterprise/federating-jira-managing-multiple-instances-461504624.html -pd

Werner, it depends on how you are viewing your issues. If it's on a dashboard, you can add the creation date as a shown field through the widget. If it just a simple query, by adding the correct column. If you are looking at issues on a board, you can add up to 3 additional fields on each card, add this one. -pd

Thanks Piotr, As a Big Picture user this is a nice resource.

Andrey, Scriptrunner can handle this with the following query: issuefunction in epicsOf("status = closed and epiclink in (a,b,c,)") If you don't have scriptrunner you could take the last part of the above, status = closed and epiclink in (a,b,c,) and run that. That would at least give you a lisk of the epiclinks for the…

Mordechai, not sure if you can get that granular. Maybe you could create a new label field for users to use. You could then make the default label field read only or remove it from the edit screen for your issues.

Lewis, try running the filter by itself. This should show you what the problem is. Correct that and save it back and your board should come back up.

Not without some serious re-engineering of JIRA.

You can always try removing the add-on and re-installing it. Although I am not entirely sure of the impact. My assumption is that and data you have would remain in the DB. Depending on what you have verify with Adaptavist at the link Nic shared above.

For this to work you will need to both allow the Anyone group access to the dashboard and access to browse issues in your projects so they are able to see the issues. If you don't add the Anyone group to the browse permission they will end up seeing a dashboard that shows no issues. No licensing restrictions around this…

Michael, not sure we can disable the emails for just likes. It looks like there was another discussion in the community regarding the disabling of the like button. It cover two options for both Cloud and Server. Good luck! https://community.atlassian.com/t5/Confluence-questions/disable-like-button/qaq-p/90327 -pd

Daniel, the non-scripting route would be a Bulk update of the JQL search results. You can update the Epic Link field through the wizard.

Not without hacking JIRA.

Your options come down to these: 1. Hack the DB (bad idea) 2. Change the original username to a new one (should work) 3. Delete all the comments made by the old account. (Also Bad) Unfortunately there are no good or recommended ways to do this. -pd