zack Specialist

Sweet! If this works for you, could you accept my answer as a solution? Thanks!

I agree with you that this would be an interesting capability to be implemented natively. My suggestion is probably more work than it needs to be, and would not scale well in large instances with multiple projects.

You could make a "Maintenance" notification scheme that does not send out Issue Updated notifications, and then temporarily change the notification scheme on the affected projects while you are doing the bulk changes, and then switch back to the proper notification scheme when bulk change are completed.

This post may also be of interest to you: https://community.atlassian.com/t5/JIRA-questions/Validator-script-to-check-status-of-all-linked-issues-before/qaq-p/427966

This could be accomplished by using the validator: "Field has been modified Validator." It would require the field (Linked Issues) to be modified during the transition. You would need to have the Linked Issues field added to the transition screen to meet the validator requirements.

This page has been an invaluable resource when I have had to work through performance issues in my JIRA instances: https://confluence.atlassian.com/jirakb/troubleshooting-performance-problems-336169888.html

I would start by looking through the JIRA log files to see if any error gets thrown during this operation. When I have encountered this in the past, it usually had something to do with data inconsistency and the index becoming impacted as a result. See here for some potentially related documentation:…

Matt, Yep. Was testing out the Article functionality of the new community with some shameless reposting. ;)

Monique, it did at one point, but those didn't last too long before they transitioned to "Drank."

Right now, about 125 different beers, and around 200 total. I've slowed down on the buying side of things; trying to focus on the drinking side. :)

The way I accomplished this was to use the REST API to change the colors of the testing environment in addition to a new site logo on the test system. Here is an example of the script I setup in crontab on the test environment to change the colors: #!/bin/sh ##TESTING ENVIRONMENT ##Change UI Colors ##Header Background…

If you are using service desk, you can setup an SLA to achieve this, and then use an automation rule to alert you when your SLA has been violated.

Unless you can use a full license on them, there is no way outside of a being a Service Desk Customer for non-users to see issues in a project. If you can use a license on them, you could add this specific group of users to your permission scheme to the Browse permission so that they have read-only access to their issues.

Here is the support portal for the Numbered Headings add-on in Confluence: https://avisi-support.atlassian.net/servicedesk/customer/user/login?destination=portals

See #3 here: Upgrade Task List Don't worry, access to JIRA Core is already included for all users have access to JIRA Software. You should be able to update Core no problem.

You need to make sure that Issue Linking is enabled in your JIRA instance (JIRA Administration>Issues>Issue Features>Issue linking) and your account will need to have the Link Issues permission in your project's Permission Scheme.

This one seems like it will require support from Atlassian. I would submit a ticket here. I have always had a great experience dealing directly with support.

Adding my vote for a linux version

You can choose to map a different LDAP attribute to the mail account used in JIRA through Advanced Directory Settings in the "User Schema Settings" section. Maybe you can make a new LDAP attribute in your Active Directory called "jira-mail" or something similar and put the email addresses you want to use in there? It would…

You will need to setup a User Directory in Confluence that pulls from your JIRA instance (Confluence Administration>User Directories>Add Directory>Atlassian JIRA). That will handle the user synchronization. Then, setting up the OAUTH application link will allow you to link you Confluence spaces to JIRA projects for…

I would take a look at this link for an idea of JIRA Service Desk and JIRA Software work together in the new model: http://blogs.atlassian.com/2014/12/collaborate-developers-using-jira-service-desk/ I would create the general Service Desk Project, and then have a Software project for each new project you have. When a…

If you have JIRA Service Desk, you could set this up using SLAs that trigger on Issue Created and Issue Resolved. If you would set the SLA to 5 days for example, the SLA would be breached for any days where it look more than 5 days to go from Created to Resolved. Unfortunately, I don't think there is a way to do this with…

I am wondering the same thing. I decided to go with the dates listed on the San Jose Convention Center's Events website here. I also went ahead and booked hotels for both weeks, because cancelling is easy once the confusion is straightened out. 

Glad it worked! Can you mark this as answered?

Can you make sure that you meet the following criteria to Bulk Edit Components: * Selected issues belong to one project, and that project has component/s * This field is not hidden in any field configurations the selected issues belong to * Current user has 'edit issue' permission for all the selected issues

In JIRA 7, you can go to Administer>Projects and choose Edit to the right of the project you want to change and choose the new project type (in this case, Software).

You may need to enable wiki-markup. Explained here: https://confluence.atlassian.com/jira/configuring-renderers-185729478.html Here is the reference sheet for formatting, including what file types are support for inline attachments: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all 

You can add images inline in JIRA comments using wiki markup. Just attach the image to the issue, and write !ImageFilename.png! in your comment.

You can use both, but they will behave in different ways. If you use a condition, you will not even have the option to transition through the workflow through the path that you set the condition on. If you use a validator, users will see the option, but will be prevented from transitioning and will be given an error…

See this article about how to set the help-paths.properties file. Particularly the "Changing the Base URL for your Help Links" section. It's a little more complicated than it should be.