Earl McCutcheon Atlassian Team

Hi Khiết, OK Got ya, and in that case you need to look at the changehistory and the changeitem tables, and we have a KB with some example queries for this including one for a specific custom field, viewable here: * https://confluence.atlassian.com/jirakb/how-to-obtain-issue-change-history-from-database-933695139.html…

Hello Jason, On the Surface it sounds like a file system permission conflict as covered in this KB article: * JIRA throws "Could not save attachment data from stream" when attempting to add attachments to issue But you did note: "Checked permissions and everything is good, even tried opening it to Everyone." and I just…

Hello Phillip, The secondary instance on the Developer license is independent from your Production system, the user count is unique to the alternate systems, and your Active User Count on the developer system is not going to change your Production license. Regards, Earl

Hey there Mark, The Versions list is going to be tied to a project, as a sub query on the Project not instance wide, and there are not any options in the API to pull a non project dependent version list, you would need to pass in the project ID for each project independently using the GET…

Hello Kelvin, I am not aware of a dedicated Connector tool through the marketplace, and as covered HERE, it looks like there is not one currently. However I found the following Article On Planview's Documentation site, that looks like the integration is possible: * Planview Enterprise and JIRA Integration But It looks like…

Hello Henry, Portfolio and the agile Board are intended for similar but separate use cases, and the Hierarchy view as seen in portfolio does not cross over into the Boards at this time. Portfolio is intended to show the Hierarchy layout on a wide view for a timeline layout on forecasting and planing and the higher…

Hello Vidya, It will be located relative to your jira-install directory. Regards, Earl

Hello Darek, This is a feature request we are tracking here: - https://jira.atlassian.com/browse/JSWSERVER-16396 Make sure to add your vote to help track interest in implementation Regards, Earl

Hello Khiết, You would want to look at the textvalue column on the customfieldvalue database table, for a custom field and the Summary is located in the jiraissue table. Additional database table details and the schema can be seen in * https://developer.atlassian.com/server/jira/platform/database-schema/ For an exe query…

Hello Iryna, As you noted "With new Jira interface" it sounds like you Upgraded Jira and the Links to confluence are no longer showing up post upgrade. Let me know if this is not the case, and please provide some additional clarification. But if this is related to an upgrade I would first recommend reviewing…

Hi Surinder, The value "Assignee" in the exe I gave is the field name where "userename" would be the variable that you want to replace. Try using this Format: assignee != surinder.sehgal AND assignee was surinder.sehgal Regards, Earl

Hello Marek, Are you using Cloud or Server? If your on Jira Server, verify the fields are using the wiki render as covered in: * Wiki markup does not work in text or comment field If your On Cloud as covered in the "The new Jira issue view" documentation, the Markup is being Phased out in favor of mark down and the option…

Hey Damien, To jump to a different project from the current when using the quick search you have to add in the "project key - issue number" where the intended functionality of adding the issue number only is to navigate to that issue in the current project. This is covered in the Quick Search Documentation under the…

Hi Ash, This is covered in the following Feature Request with a suggested workaround: - https://jira.atlassian.com/browse/JRASERVER-62216 Make sure to add a vote to the feature to help us track interest in implementation Regards, Earl

Hello Surinder, JIRA does not natively store the users that were assigned to an issue to a field that can be viewed as a list, but you can poll against the assignee field using the WAS Operator. On a user by user basis the JQL "assignee != username AND assignee was username" could give you a issue list of issues that the…

Hey There Emma, Depending on your environment it could be a couple things. Are you using the new Project Archiving method currently only available on Jira Data Center as covered HERE Or are you using the Alternate method of removing user permissions as covered HERE? If this is in Datacenter on the New Feature Please file a…

Hello, There are Two Issue Import options for CSV, under the Issue Dropdown "Import Issues from CSV" does not allow mapping to existing issue using the issue key and will allow you to Bulk create new issues. If you need to update existing issues navigate to Admin >> System >> IMPORT AND EXPORT >> External System Import >>…

Hello Robert, Check that the Status is mapped to a column on the board as covered HERE Regards, Earl

Hi Julien, You are going to want to make a copy of the Production database and point the dev instance to the new DB to align the data to the Prod system, the Full step by step for setting this up can be seen here: * Establishing staging server environments for Jira applications Regards, Earl

Hello Amine, This is covered in the Documentation in Creating and deleting plans but there are some hard set limits on the plans for what can be imported or rendered that are set for performance reasons to prevent overloading the system as these are resource intensive operations. The Hierarchy level is disabled for the…

Hi Nikita, Glad I could help out, and please mark this as answered unless you have any follow up questions so it will be easier for others to find. Regards, Earl

Hi Jerry, I think the best option for that is to use a filter in a API issue search result set pulling the data using the Rank: /rest/api/2/search?jql=<FILTER HERE>&maxResults=# Please see this doc for some examples on passing JQL via API: * JIRA Developer Documentation : JIRA REST API Example - Query issues Noting that…

Hi Tina, The Dependencies are tied to Issue Links, by default Portfolio only as the link type Blocks configured but additional dependencies can be configured, when an issue is linked to another issue and the Dependency is mapped to the link type, the dependency is set on the issue and the report automatically pulls in the…

Hi Ben, Since this is happening for a single user is most likely permission related. And from the behavior you described I suspect Workflow properties or Issue Secuety. Check the Workflow Properties on the DONE status on the subtask workflow to see if there are any permission based properties that might exclude that user.…

Hello Velijko, The Assignee Field is a Customized System Field and there is not a Field type Identical to the behavior of assignee. The Closest thing you can use is a User Picker single select Custom field type, some details on this can be seen here: - How does the user picker work in JIRA applications There is also the…

Hey There Thomas, We Put out Blog Posts on topics such as this on a regular basis and I collected a few that I would recommend looking over: * 6 steps to better release management in Jira Software * A product manager’s guide to release planning * Best Practices: Strategies for Defining your JIRA Projects * Three…

Hello Pawel, Natively Jira does not have a mechanism to update a field based on another field being update. I'd suggest using the Script Runner add-on, which has a functionality named Scripted Fields. With these, you can create two fields that would take its value based on what's set on the other field. Documentation and…

Hello Miriam, You are going to want to look into the JQL Functions added in by ScriptRunner For Jira, that add in a subtaskOF() jql function detailed at the link below that I believe will accomplish what you are looking for: * Adaptavist Scriptrunner: subtasksOf(Subquery) Using this Function you could do something like:…

Hi Nikita, We have a feature Request to add this in viewable here: * For the Server Platform * For the Cloud Platform Make sure to add your Vote to the request to help us track interest. Regards, Earl

Hello Jack, The JIRA Rest API does not support authentication for a user once JIRA's CAPTCHA upon login feature has been triggered for that particular user, which is a mechanism to prevent Brute Force login attempts. Reseting the users failed login count in the UI under user management will get you back on track, OR as…