Earl McCutcheon Atlassian Team

Hi Clayton, Yes that is correct, there needs to be a time based data point in place for the algorithm to make time based calculations to be able to put the issue on the schedule within that allotted timeframe. The document Scheduling behavior goes over the data point scheduling factors in more detail. Regards, Earl

Hello Megha, The method you noted is how you are able to increase the limit but there is a limit for a reason & the performance hit when increased is the side affect of doing this. Bulk operations are slow and resource intensive. It's not recommended to increase this value. The best approach would be to 5 batches of 1000…

Hello Jason, Details on Mapping the statuses to the columns can be found in This Article. But I do want to point out that the Statuses cannot transition vertically within the same column as covered in the following Feature Requests: * https://jira.atlassian.com/browse/JSWCLOUD-3573 *…

Hello Aaron, Add the 'Update Issue Field' post-function to that transition used between the two columns, which has resolution field as an available field. Regards, Earl

Hi Matthew, This is not currently available for the description fields in Portfolio. We have the Following Feature Request for this so please add your vote to help us track interest in implementing this a new feature: * https://jira.atlassian.com/browse/JPOSERVER-387 Regards, Earl

Hello Radosveta, Instead of creating a new SLA, I believe what you are looking to do can be accomplished by setting a "no target" value for the Goals section of the existing SLA using JQL to filter out the issue type that you do not want to , with something like this: you could do the search on the Field, either Issue…

Hello Steven, This is not something that can be modified in the velocity chart, the chart requires completed sprints to be able to populate the data from the historical data, and cannot be preemptively configured. Alternatively, you can create a team and set a velocity setting for that team using Portfolio for jira as…

Hello Kapli, You can set the Issue security level directly in the database, Generally Direct DB modification is not recommended unless you can verify the change is safe, but I can verify this one is safe from extensive testing I performed when writing up that BUG you noted. But any time a Direct DB update is done make sure…

Hello David, When you commit the changes you are finalizing the data point and updating the jira issues directly, and there is no undo option once commited. Regards, Earl

Hi Glen, Thanks for the info and I was able to reproduce the error without issue and this is defiantly a new BUG, I filed the following request to track this: * https://jira.atlassian.com/browse/JSDSERVER-5944 Playing around with the browser setting a bit I was not able to find a more graceful workaround other than simply…

Hello Clayton, With Portfolio for Jira, if you have a release scheduled, and you have an issue scheduled to complete before, portfolio is going to add that issue to the release. Please see "Using the later release" for more details on the release calculation. If you do not want an issue to be calculated into a releases use…

Hello, There are two primary reasons to see this error the first is that the captcha was indeed answered incorrectly OR if the user did answer the CAPTCHA correctly and still received the warning, then something in the in the browser cookies is erring as covered in This KB article. Have the user clear out browser cache &…

Hi Glen, Edge is supported and we should not see any differences in the links response behavior between chrome and edge, so this defiantly sounds like a BUG. Can you please provide some more details on the steps to reproduce and I will see if I can reproduce this locally, primarily: * what links in the portal are you…

Hello Travis, This is not currently possible, we have a feature request tracking interest in implementation viewable here: * https://jira.atlassian.com/browse/JPOSERVER-525 Make sure to add your vote to help us track continued interest in the feature. Regards, Earl

Hello, The default workflow can't be changed, its set as read only intentionally as making changes to it can cause issues. What you can do however is create a copy of the default, make any desired modifications the new workflow (i.e. the statuses you are looking to import), and configure a scheme and projects to use this…

Hi Subhajit, Check out the following community post that gives a exe on how to accomplish this using Javascript injections from the description of a field on the particular screen in use: * https://community.atlassian.com/t5/Jira-questions/Hide-select-lists-of-Project-and-Issue-Type-from-the-Create/qaq-p/241794 Another…

Hey There Henry, It looks like you have already covered a lot of ground on this one, and thanks for all the details. As mentioned in the alternate thread you mentioned with similar errors the next steps recommended before the alternate workaround was noted which you tried without success, was to set up a new empty…

Hello Ramesh, To change the status you will need to transition the issue Check out: * JIRA Server platform REST API reference: Do Transition Use the format: curl -D- -u user:pass -X POST --data {your-json-data} -H "Content-Type: application/json" http://<BASE_URL OR…

Hello, Can you provide some additional info on the environment, as I can see in your screenshot that the instance name is "happy-test" and I am wondering if this is this a new staged instance that recently had an import for a test migration? Because, if you didn’t include attachments in backup file or included them but…

Hey Bella, I was trying to look into this for you and I do not recognize that settings menu from the screenshot as a native option in Jira, is that part of an add-on, and do you know which one? Also what is the navigation path you are following to get to that menu as this might give me better context as to what this is,…

Hello Micah, I did some testing on this and the EndPoint is Posting without issue when i'm doing this locally using curl and postman: curl -D- -u user -X POST --data "{\"issues\": [\"ASDF-9\"]}" -H "Content-Type: application/json" "http://<BASE_URL>/jira760/rest/agile/1.0/sprint/37/issue" And looking at this I would guess…

Hi Raj, In the Description Field, this should not be an issue, EXE test in jira 7.6.0: Editing In Visual mode: Editing In text Mode: Saved: A few troubleshooting steps to help narrow this down: * What version of jira are you on? * What is the render on the Description field currently set to? * Check for local Browser…

Hello Again, Also On the Screen, check the Jira Admin Helper "Where is my field?" option, to see if to identifies the issues. Regards, Earl

Hi Faisal, Use duedate all lowercase one word, and it should work for you: Regards, Earl

Het there John, The Time in source status will track the total ammount of time an issue was in the last status before transitioning to the next status. As an EXE: a workflow with ToDo >> InProgress >> Done with all transitions set as global (All to all) there are 9 possible transition: * ToDo > ToDo * ToDo > InProgress *…

Hi Charlie, Erratic behavior like this sounds most likely to be a Browser issues as you touched on, i would recommend starting with this Guide that has some basic troubleshooting steps to help narrow this down: * Browser Troubleshooting Guide I would also recommend Loading up the Javascript console in your browser to see…

Hello Jon, As an Epic by Epic Search in JQL you can use "parentEpic()" Also Check out this Previous Post on this topic, it offers up some recommended add-ons to go more granular and provide even more details: *…

Hi Jason OK I got you now, and thanks for the clarification, I did some more testing and see what you are talking about. The Feature Request was in regards to hiding the SLA field in the field configuration when you have SLA metrics configured, Not the SLA tag showing up as an empty toggle item if you do not have any SLA's…

Hi Theresa, Thanks for the Screenshot, and this is defiantly the BUG I noted: * https://jira.atlassian.com/browse/JRACLOUD-67792 This BUG currently does not have a Workaround, so make sure to add your self as a watcher to get updates on the status of the fix. As this is defiantly the bug there is no need for follow up info…

Hi Juanita, Thanks for the screenshot, and it looks like there is a bit more data behind the scenes coming into play. The capacity itself is going to have quite a few reasons that there is Free capacity left over. The main thing to consider is that the scheduling algorithm believes there is nothing is able to schedule at…