Iwantloading403

1. Phpstorm Jira Software
2. Phpstorm Jira Download
3. Intellij Community Edition

When I try to connect to Jira using the Atlassian plugin (3.0.16), I have to enter a captcha when my password is changed. But there is no browser, so I don't see a captcha. I have made a connection to Jira before using the browser (after I had to change my password) and entering the captcha, but apperently this is considered a different connection. My team has a Jira project on Atlassian servers. How can I connect that project with IntelliJ IDEA IDE? When creating a connection from IntelliJ to Atlassian, I need the server name and username w.

This page tells you how to configure your Atlassian Connector within IntelliJ IDEA. Before following the steps below, please make sure that you have installed the connector, as described in the Installation Guide.

Phpstorm Jira Software

The connector configuration panels display the version number and the SVN repository version of the Atlassian Connector that you are currently using.

The Atlassian Connector for IntelliJ IDEA stores configuration settings at two levels in IntelliJ IDEA:

• Server connections are stored as project settings in IntelliJ IDEA. Project settings allow you to share the same server connections with other members of your project team. Additionally, if you work on more than one project, this allows you to configure different servers for each project. Project-level settings can be stored in your source control repository, so that the connector will load the settings at the same time as loading the project into IDEA.
• Other options are stored as IDE settings in IntelliJ IDEA. IDE settings allow each developer to configure their own workspace-specific settings, such as polling intervals and the behaviour of notification popups.

On this page:

• Configuring your General Options
• Configuring a Default Username and Password
• Configuring Servers and Display Options

Configuring your General Options

Screenshot: General tab of the connector's IDE Settings panel

The 'General' tab is used to define the upgrade options for your connector, configure an HTTP proxy and set other options as described below.

To access the general options:

1. Go to the 'IDE Settings' for the 'Atlassian Connector', by doing one of the following:
   • Open the IDEA 'Settings' dialogue, then go to the 'IDE Settings' section and click the 'Atlassian Connector' icon.
   • Or you can click the configuration icon on your connector window.
2. Click the 'General' tab.

Automatic Upgrade

The connector's auto-upgrade feature, if enabled, will prompt you to install the most recent version of the connector when available.

To configure the connector's auto-upgrade feature:

1. Put a tick in the 'Enabled (stable version)' checkbox to enable the connector auto-upgrade feature. The connector will check for the latest available stable (released) version of the connector.
2. Put a tick in the 'Check snapshot versions' checkbox if the auto-upgrade should include unstable (development) versions of the connector as well as stable versions.

Manual Upgrade

To check immediately for the latest version of the connector:

1. Select one of the radio buttons as follows:
   • Stable only — The connector will check for the latest available stable (released) version of the connector.
   • Stable + snapshot — The connector will check for the latest version, including unstable (development) versions of the connector as well as stable versions.
2. Click the 'Check now' button.

For more details, refer to Upgrading the IntelliJ Connector.

HTTP Proxy

You can configure the connector to use IDEA's proxy settings or to bypass IDEA's proxy settings altogether. If the connector is using IDEA's proxy settings, you can configure the settings here too.

To use IDEA's proxy settings:

1. Select the 'Use IDEA proxy settings' radio button.
2. Click the 'Edit IDEA proxy settings' button. A dialogue will appear, similar to this screenshot:
   
3. Enter the required settings and click the 'OK' button. If your proxy requires a domain name in addition to username, enter the information in the format domainuser.
4. Restart IDEA for your changes to take effect.

Direct Click Through

When the direct click through option is enabled, you can click through from Crucible to open a review directly at the relevant code line in IDEA.

Check the 'Enable Direct Click Through' checkbox.To configure the direct click through feature:

1. Choose a different TCP/IP port if necessary. Note that if you change this setting, you will need to restart IDEA to apply the change. This will have the effect of starting and stopping the inbuilt HTTP server.

Collection of Statistics

Put a tick in the 'Report anonymous usage statistics' checkbox if you are happy for us to collect anonymous information on the way you use the connector. All the information we collect is anonymous and cannot be used to identify you. We do not collect any private information. We use a randomly generated unique ID to differentiate one installation from another. See Collecting Usage Statistics for the IntelliJ Connector.

Configuring a Default Username and Password

You can define a single username and password as default login credentials. You can then decide to use these default credentials for one or more of the servers that you configure for the connector.

Defining the Default Credentials (Username and Password)

There are two ways to define your default credentials:

• When you supply your credentials for a server, the connector will ask whether you want to use these credentials as the default. Click 'Yes'.

Screenshot: Popup offering to use default credentials

• Otherwise, you can define the default credentials on the 'Defaults' tab of the connector's 'Project Settings' panel:
  1. Open the IDEA 'Settings' dialogue.
  2. Go to the 'Project Settings' section and click the 'Atlassian Connector' icon.
  3. Click the 'Defaults' tab.

Screenshot: Defaults tab with the default credentials at the bottom

Using the Default Credentials (Username and Password)

You can use your default credentials for one or more of the servers that you configure for the connector:

1. Still on the connector's 'Project Settings' panel, click the 'Servers' tab.
2. Select the relevant server.
3. Put a tick in the 'Use Default Credentials' checkbox.

Configuring Servers and Display Options

Configuring your JIRA Server Connections

To configure your JIRA server connection(s):

1. Go to the 'Project Settings' for the 'Atlassian Connector', by doing one of the following:
   • Open the IDEA 'Settings' dialogue, then go to the 'Project Settings' section and click the 'Atlassian Connector' icon.
   • Or you can click the configuration icon on your connector window.
2. Go to the 'Servers' tab.

To add a JIRA server:

1. Click the plus icon on the configuration panel.
2. A list of server types will appear. Select 'Add JIRA Server'.
3. A form will appear. Enter the information as follows:
   • 'Server Enabled' — Leave this checkbox ticked (default). If necessary, you can remove the tick to disable particular servers without deleting them. This is useful if your servers are behind a firewall and you don't have access to them.
   • 'Server Name' — A description of your JIRA server.
   • 'Server URL' — The address of your JIRA server.
   • 'Username' and 'Password' — The login name and password you use to access the JIRA server.
   • Remember Password — Put a tick in the checkbox if you want to save your password on disk. Leave the checkbox unticked if you want to be asked for a password every time you start your IDE.
     If you choose to remember the password, it is stored in a Base64 encoding, so it is not really secure.
   • 'Use Default Credentials' — Put a tick in the checkbox if you want to use the single username and password that you have defined as your default credentials. You can set the default credentials on the 'Defaults' tab.
4. If you want to use basic HTTP authentication for your JIRA server, fill out the fields in the 'Additional Configuration' section as follows:
   • 'Use Basic HTTP authentication' — Tick this checkbox.
   • 'Username' and 'Password' — The login name and password you use to access the JIRA server.
5. Click the 'Test Connection' button to check that the connection to the server works.
6. Click 'Apply' to save your changes and continue with server configuration, or 'OK' to save your changes and close the configuration tab.
7. Click the 'Defaults' tab to set your default server (if you have defined more than one JIRA server) and default project.
8. Now you can configure the JIRA options, as described below.

You can add more than one JIRA server.

Configuring your JIRA Options

1. Open the IDEA 'Settings' dialogue, then go to the 'IDE Settings' section and click the 'Atlassian Connector' icon.
2. Define the maximum number of issues that the connector will show on each screen. At display time, if there are more issues than specified here, the connector will display a 'Get More Issues...' link allowing you to retrieve the next batch of issues from the server.

Screenshot: Configuring JIRA server connections
Screenshot: Configuring JIRA IDE options

Configuring your Bamboo Server Connections

To configure your Bamboo server connection(s):

1. Go to the 'Project Settings' for the 'Atlassian Connector', by doing one of the following:
   • Open the IDEA 'Settings' dialogue, then go to the 'Project Settings' section and click the 'Atlassian Connector' icon.
   • Or you can click the configuration icon on your connector window.
2. Click the 'Servers' tab.

To add a Bamboo server:

1. Click the plus icon on the configuration panel.
2. A list of server types will appear. Select 'Add Bamboo Server'.
3. A form will appear. Enter the information as follows:
   • 'Server Enabled' — Leave this checkbox ticked (default). If necessary, you can remove the tick to disable particular servers without deleting them. This is useful if your servers are behind a firewall and you don't have access to them.
   • 'Server Name' — A description of your Bamboo server.
   • 'Server URL' — The address of your Bamboo server.
   • 'Username' and 'Password' — The login name and password you use to access the Bamboo server.
   • Remember Password — Put a tick in the checkbox if you want to save your password on disk. Leave the checkbox unticked if you want to be asked for a password every time you start your IDE.
     If you choose to remember the password, it is stored in a Base64 encoding, so it is not really secure.
   • 'Use Default Credentials' — Put a tick in the checkbox if you want to use the single username and password that you have defined as your default credentials. You can set the default credentials on the 'Defaults' tab.
4. Click the 'Test Connection' button to check that the connection to the server works. A list of build plans will appear.
5. If your Bamboo build server is located in a different time zone than you, you can manually adjust the 'Time Zone Difference'. You should specify a positive difference if your time is ahead of your build server (e.g. you are in Russia and the build server is in the UK). You should specify a negative difference if your time is behind your build server (e.g. you are in the US and your build server is in Spain).
6. Now select the Build Plans that the connector will watch. You can either select plans manually from the list of plans defined on the Bamboo server, or simply use your favourite plans as defined on the server. Your favourite plans are marked with a yellow star .
7. Click 'Apply' to save your changes and continue with server configuration, or 'OK' to save your changes and close the configuration tab.
8. Now you can configure the Bamboo options, as described below.

You can add more than one Bamboo server.

Configuring your Bamboo Options

1. Open the IDEA 'Settings' dialogue, then go to the 'IDE Settings' section and click the 'Atlassian Connector' icon.
2. Define the behaviour of the popup window that is shown when the status of the build changes. (See Working with Bamboo Builds in IDEA.)
3. Set the polling interval that the connector will use to monitor build plans on all defined Bamboo servers. Specify the value in minutes.

Configuring your Crucible Server Connections

To configure your Crucible server connection(s):

1. Go to the 'Project Settings' for the 'Atlassian Connector', by doing one of the following:
   • Open the IDEA 'Settings' dialogue, then go to the 'Project Settings' section and click the 'Atlassian Connector' icon.
   • Or you can click the configuration icon on your connector window.
2. Click the 'Servers' tab.

To add a Crucible server:

1. Click the plus icon on the configuration panel.
2. A list of server types will appear. Select 'Add Crucible Server'.
3. A form will appear. Enter the information as follows:
   • 'Server Enabled' — Leave this checkbox ticked (default). If necessary, you can remove the tick to disable particular servers without deleting them. This is useful if your servers are behind a firewall and you don't have access to them.
   • 'Server Name' — A description of your Crucible server.
   • 'Server URL' — The address of your Crucible server.
   • 'Username' and 'Password' — The login name and password you use to access the Crucible server.
   • 'Remember Password' — Put a tick in the checkbox if you want to save your password on disk. Leave the checkbox unticked if you want to be asked for a password every time you start your IDE.
     If you choose to remember the password, it is stored in a Base64 encoding, so it is not really secure.
   • 'Use Default Credentials' — Put a tick in the checkbox if you want to use the single username and password that you have defined as your default credentials. You can set the default credentials on the 'Defaults' tab.
4. Click the 'Test Connection' button to check that the connection to the server works.
5. Click 'Apply' to save your changes and continue with server configuration.
6. Click the 'Defaults tab to set up a default Crucible server, project and repository. These defaults will be used when you create a review directly from your source within IDEA.
7. Now you can configure the Crucible options, as described below.

You can add more than one Crucible server.

Removing a Server Connection

To remove a server from the list:

1. Select the server.
2. Click the minus icon on the configuration panel.

Reporting Bugs and Requesting New Features

Phpstorm Jira Download

Click the following links on the Project Settings or IDE Settings panel:

• Report Bug — This will open a bug-creation page in the connector's JIRA issue tracker. It will automatically populate the connector version number and details of the environment (Java version and vendor, OS details, build number of your IDE).
• Request Feature — This will open an issue-creation page of the 'Story' type in the connector's JIRA issue tracker. Use this issue type to request new connector functionality.

Getting Help

Click the 'Help' link on the Project Settings or IDE Settings panel. This will open the online documentation page which tells you how to configure the connector — namely, this page. From here, you can click the links to view other online documentation pages.

If you're looking for support or other help, please take a look at the links on our documentation home page.

RELATED TOPICS

Installation and Upgrade Guide for the IntelliJ Connector
Using Bamboo in the IntelliJ Connector
Using Crucible in the IntelliJ Connector
Using FishEye in the IntelliJ Connector
Using JIRA in the IntelliJ Connector

When you work on a project, you can organize your work in smaller tasks that you need to complete.

These can be tasks that you set yourself. In PhpStorm, you can divide a large piece of work into smaller tasks and associate them with changelists.

Or these can be tasks coming from your issue tracker. For example, you can work with tasks and bugs assigned to you directly from PhpStorm. To be able to do so, connect the IDE and your tracker account.

Before you start working with tasks, make sure that the Task Management plugin is installed and enabled.

Configure integration with issue trackers

PhpStorm supports integration with:

Connect the IDE to your tracker

1. In the Settings/Preferences dialog Ctrl+Alt+S, select Tools | Tasks | Servers.

2. Click and select the necessary issue tracker from the list.

3. Enter connection details. Note that settings differ depending on your issue tracker.

   Normally, you have to specify the server URL and connection credentials: Username and Password.

   In some cases, you can enter an API token in the Password field instead of your password.

4. Select the Share URL option to allow access to the server for other members of your team. When this option is enabled, a server URL and its type are saved to the .idea/misc.xml file, which can be shared between development team members through version control.

5. Click Proxy settings if you want to access the server via a proxy server. You can find more information on proxy settings in the HTTP Proxy section.

6. On the Commit Message tab, you can enable adding a commit message for a changelist and configure a message template.

7. On the Server Configuration tab, configure advanced parameters for connecting to your issue tracker.

   This tab is only available for some trackers (for example, for trackers that are not supported out of the box ).

   Code completion is available in the fields on this tab.

Refer to the Configuring Generic Task Server tutorial for an example on how to configure these parameters.

Specify additional integration options

1. In the Settings/Preferences dialog Ctrl+Alt+S, select Tools | Tasks.

2. Configure the necessary options:

   • Changelist name format: when you open or create a new task, PhpStorm prompts you to create a new changelist associated with this task. In this field, you can specify a template that will be used for generating names for new changelists.

     Click to select placeholders from the list.

   • Feature branch name format: when you create or open a new task, PhpStorm prompts you to create a new feature branch. In this field, you can configure the template for generating names of new feature branches.

     Click to select placeholders from the list.

     Use the Lowercased and Replace spaces with options to configure prompted feature branch names.

     These settings are useful if your IDE is integrated with an issue tracker. For example, the DSGN-0001 Add new icon task name is going to be converted to the dsgn-0001add-new-icon feature branch name.

     You can always modify a feature branch name before creating it if the generated name doesn't work for you.

   • Task history length: the number of tasks that PhpStorm stores.

   • Save context on commit: every time you commit changes, PhpStorm creates a new closed local task that keeps files, bookmarks, and breakpoints that you have worked with. This way, you can quickly restore all tabs associated with the task any time in the future.

   • Enable issue cache: optimize synchronization between PhpStorm and your issue tracker. Synchronization is especially recommended if you work with 'slow' issue tracking systems.

     PhpStorm caches the list of issues loaded from the tracker and updates them repeatedly. You can specify how many issues should be cached and how often PhpStorm should update information about them.

Tasks

In PhpStorm, there two types of tasks:

• Tasks that were loaded to PhpStorm from your issue tracker. These are tracker tasks Tracker tasks are linked with the corresponding issues in your issue tracker. This allows you to monitor and update them directly from PhpStorm.

• Tasks that were originally created in PhpStorm. These are local tasks. Local tasks are not related to an issue tracker.

If you have created at least one task of either type, a list called task combo becomes available on the toolbar.

Open tracker tasks

Tracker tasks are loaded to your PhpStorm once you connect it to your issue tracker.

1. From the main menu, select Tools | Tasks & Contexts | Open TaskAlt+Shift+N, or click the task combo on the toolbar.

2. Select the necessary task from the list.

3. In the Open Task dialog, you can update issue state.

   If you want to close all tabs that are currently opened in the editor, select the Clear current context checkbox.

4. In the VCS operations section, you can create a new changelist, select an existing branch to which you want to contribute, or create a new one.

   You can also shelve the current changes to return to them later.

Create local tasks

In PhpStorm, you can create local tasks that do not originate from your issue tracker.

1. From the main menu, select Tools | Tasks & Contexts | Open Task. You can also use the task combo or press Alt+Shift+N.

2. In the Enter task name dialog, select Create New Task.

3. Enter a name for the new task.

   If you want to close all tabs that are currently opened in the editor, select the Clear current context checkbox.

4. In the VCS operations section, you can create a new changelist, select an existing branch to which you want to contribute, or create a new branch.

   You can also shelve the current changes to return to them later.

View task description

When you are choosing a task to switch to, the list of tasks shows only task IDs. This information is not always sufficient, because it reflects neither the steps that lead to the problem nor the related discussion.

1. Go to Tools | Tasks & Contexts | Open Task.

2. Open the necessary task and press Ctrl+Q to open the task description in PhpStorm, or Alt+Shift+B to view the description in a browser.

Alternatively, go to Tools | Tasks & Contexts and click Show ' task ID' Description or Open ' task ID' in Browser.

View closed tasks

A closed local task is a task that is not associated with a changelist if the entire project or the affected directory is under a version control.

A closed tracker task is a task that has the closed status in your the issue tracker.

1. Click the task combo and then click Open Task.

2. Select the Include closed tasks checkbox, or press Alt+Shift+N.

Close tasks

• Go to Tools | Tasks & Contexts and click Close Active Task.

This will close the current context in the PhpStorm. Select the necessary checkboxes to commit changes and, optionally, merge the branch that was created. For tracker tasks, you can also change their state. The new state will be propagated to your issue tracker.

Delete tasks

If you do not need a task to appear in PhpStorm, you can remove it from the list of tasks.

1. Click the task combo on the main toolbar.

2. Select one or more tasks you want to delete.

   Use Shift (for adjacent items) or Ctrl (for non-adjacent items) keys for multiple selection.

3. Click the right-arrow button, and select Remove.

When you are deleting tracker tasks, you remove them from the IDE. They will remain in your issue tracker. Local tasks in this case will be completely removed, since they are not connected to your issue tracker.

Time tracking

Before you start, make sure the Time Tracking bundled plugin is enabled in the Installed tab of the Settings/Preferences | Plugins page as described in Managing plugins.

With PhpStorm, you can track the amount of time you spend on a task working in the editor. For local tasks, this information might be helpful if you want to know how much time exactly you need to compete a task as you work on a project.

For tracker tasks, this option is useful if your issue tracker configuration requires that you log the time you spend on tasks. In this case, you can send your time log from PhpStorm to the tracker.

Enable time tracking

1. In the Settings/Preferences dialog Ctrl+Alt+S,

   go to Tools | Tasks | Time Tracking and select the Enable Time Tracking checkbox.

2. (Optionally) Change the Suspend delay value.

   Here you can specify how long you have to stay inactive before the task will be considered suspended.

Track time

• Click for automatic time logging.

  For manual time tracking, click . To stop manual time tracking, click .

To reopen the Time Tracking tool window, select View | Tool Windows | Time Tracking.

Send time log to tracker

1. Click Post work item to bug tracker in the Time Tracking tool window.

2. Specify time interval you want to log and add a comment if necessary. Click OK.

Contexts

A context is a set of bookmarks, breakpoints, and tabs opened in the editor. Contexts are linked to tasks, but you can work with contexts without associating them with specific tasks.

Having separate contexts lets you work on several things and switch between them without mixing the changes.

You can view the list of bookmarks and breakpoints in the Favorites tool window.

Save a context

1. From the main menu, select Tools | Tasks & Contexts | Save Context.

2. In the Save Context dialog, enter the name of the context and click OK.

Add items to existing contexts

Intellij Community Edition

1. From the main menu, select Tools | Tasks & Contexts | Load Context.

2. Add the necessary items (bookmarks or breakpoints) or open the necessary files and save the context: Tools | Tasks & Contexts | Save Context.

Switch between contexts

When you switch between tasks, the IDE automatically switches related contexts. However, if the contexts that you work with are not associated with tasks, you can switch between them manually.

1. From the main menu, select Tools | Tasks & Contexts | Load Context.

2. In the Load Context popup, select the necessary context from the list.

   Alternatively, click the right arrow and select Load.

Clear a context

• To clear the current context without loading another one, select Tools | Tasks & Contexts| Clear Context from the main menu, or press Alt+Shift+X.

Delete a context

When a task is finished, or if you do not need a context anymore, you can remove it.

1. From the main menu, select Tools | Tasks & Contexts | Load Context.

2. In the Load Context popup, click the right arrow and select Remove.