Comments
-
Thanks for sharing!
-
In my opinion, JIRA workflows are tools for: * optimizing collaborative interactions among people working on phases of the same task * help with reporting Zephyr test 'executed statuses' are queryable through ZQL (some additional functions to JQL). This is the ZQL reference. I've never used Zephyr, but I think that…
-
Do you mean you use a tool for Unit Testing and would like to integrate it with JIRA, so that when a test is passed, its linked JIRA task transitions to Done? If that's the case, what tool do you use?
-
Haha, seems like we are in the same page
-
Can you define how do you 'Pass' an issue in the project? In other words, what action should trigger the automatic transition from To Do to Done?
-
Hi Adrian, When that happens, it is probably because at least one of the following causes (extracted from the same doc page I pasted before): Board troubleshooting Why can't I see issues on the board? If your project contains customized workflows, you might not be able to see your issues on the board. Here are the two main…
-
Issues disappear from the board after 14 days of having been resolved. Could that be the case? If that's the case, click on the link "Looking for an older issue?" in the most-right column to show them again. More info about Business Boards: https://confluence.atlassian.com/jiracorecloud/working-with-boards-800712866.html
-
Do you belong to the site-admins group, besides of the group administrators?
-
It refers to SSH public and private keys, which you should generate: https://help.github.com/articles/generating-an-ssh-key/ You can even generate a pair online: http://travistidwell.com/blog/2013/09/06/an-online-rsa-public-and-private-key-generator/
-
The Status Resolved is not the same thing than the Date Field Resolved (also known as resolutiondate). You can set your workflow so that, on entering Resolved status, a resolution is automatically set (or, alternatively, popup a dialog to set a resolution). As soon as an issue has a value on the field Resolution, the date…
-
It has been created a new issue for keeping track of this recurrent issue: https://jira.atlassian.com/browse/JRA-61835
-
Just to complement Nic's correct information, if you do not know how to set a property follow these steps: * Find the workflow of the project you want to modify and click on Edit. * In the Diagram mode, click on the status you want to apply the property. A panel will be shown on the right side. * Click on the 'Properties'…
-
Oh, I found it: jira.permission.edit.group=jira-administrators Thanks
-
@Nic Brough [Adaptavist] How exactly can you exclude a group from being affected by the "jira.issue.editable = false" property?
-
The Closed status might have a property that forbids editing the issue. * Find the workflow of the project to which the affected issue belongs and click on Edit. * In the Diagram mode, click on the Closed status. A panel will be shown on the right side. * Click on the 'Properties' link from the panel. A new tab will be…
-
Check these 4 bullets: An issue will only be visible in the Backlog if: * the issue is not a sub-task, * the issue matches the board's saved filter, the issue's status maps to one of the board's columns (but not the Done column), and there is at least a status being mapped to the right-most column. e.g. If you have the…
-
Is the board configured to use any swimlanes? If so, based on what?
-
Do you confirm that the issue is being shown in the JQL search while the issue belongs just to the inactive sprint?
-
That's really strange... Some random questions: When the backlog is being loaded without the issue, are there any errors in your browser's console? Have you tried reproducing the same weird behaviour in a different browser? Sometimes there could be problems with your browser's cache.
-
Assuming you want a Done task to be removed from the board of your JIRA Core project, read this quotation from this documentation: * Issues disappear from the last column after 14 days of inactivity. Select the link at the bottom of this column to see them again.
-
If you have already installed the addon, then you just have to wait until the free trial period ends, and after that, you will be charged the addon's fee to the account you have set as your payment method on your instance. Once the trial period had ended, you will be able to see the estimate of your next bill here:…
-
Try this URL: https://YOURS.atlassian.net/secure/project/ViewProjectRoles.jspa where YOURS is your Cloud instance's subdomain name. You will find the option at the bottom of the page. By the way, are you from Santander? (cause I am) Regards
-
+1'ed.
-
It might be difficult to obtain anything that looks and works exactly as you described but, as you described the purpose as well, I will put here a similar solution that might work for you: * Create a new issue of type Story and add to it all subtasks shown in your screenshot. * Create a board with three columns, named To…
-
I have added your suggestion here: https://jira.atlassian.com/browse/JRA-59874 You can vote for it. Regards.
-
I agree this can be improved. You might want to create a suggestion here: https://jira.atlassian.com/projects/JRA/issues I will vote for it!
-
You don't need to uninstall the old addon. Try this URL, changing it to match your instance: https://YOURS.atlassian.net/plugins/servlet/upm/marketplace/search?q=Time%20Reports%20and%20Gadgets%20for%20JIRA%20Cloud
-
As Heidi has stated, it is very likely that you have edited an active workflow, meaning that you had been editing a draft instead. Please, double check that the draft had actually been published.
-
Nearly simultaneous! +1'ed
-
Try this JQL: assignee was currentUser()