Yves Riel _Okapya_ Atlassian Partner

What about if you create the Bug as a subtask for the Story? This way you don't have to link it and it will automatically appear in your Sprint. You could also create a new subtask type for that.

Not sure it will completely address your needs but you may want to take a look at the Checklist plugin. The checklist may have by default the text in bold and the user can complement the description before checking out the item.

Hi Angus, There was no particular plan for this but checking at the data center documentation, customfields should not have anything to do for Data Center thus it should work out of the box.

Hi ASE Admin, Although we should avoid as much as possible linking hours to story points, there are times where this can become useful. One such case is when we want to monitor the health of our estimation process. Based on this, we can effectively correct bad estimation practices. There is an add-on on the Atlassian…

Sorry Edouard, Checklist doesn't have a cloud version so you will not be able tom import the data to the cloud.

If you still want to have global items in the new instance, you will have to create the options nonetheless. The export functionality was created to allow users to generate templates. They could store this in a text file somewhere and quickly paste them in the new issue.

Hi Shane, Export will only export the items that are at the issue level. Options, which are items global to all issues, are not exported because they will be automatically created when a new issue is generated. Regards

I know it is an old post but in case someone eventually looks for this ... Personnally, we have tried pinning a Definition of Done (DoD) in front of the developers at their desk but it was not always a success. We eventually embedded it in their worklow within JIRA. They have a custom field listing the items of the DoD and…

It is not the first time a problem is reported within Service Desk. Service Desk activates save-on-blur by default which is incompatible for Checklist. See this issue reported to Atlassian last fall. You may want to vote for it and even write a comment to Atlassian about this There also seem to have a work-around by going…

Hi Jeremy, Can you please provide more information? This has never been reported before so I would need more information. Is this problem reproducible? If so, what is the sequence of steps to reproduce it? I small video could help too. Can you check in the JIRA logs to see if any Checklist errors are logged? Thanks

Hi Andy, Is this the same question as you asked here? Or is it something different?

You're welcome and good luck with evaluation of Checklist!

Hi Gary, When you edit the checklist, do you see the textarea at the bottom? This is where the checklist items are entered on the issue itself. Take a look at this: https://okapya.atlassian.net/wiki/display/CHK/Editing+a+Checklist Yves

Could be that the board owner does not have access to the other filters. Make sure that all filters are Shared.

Hi Hudson, We initially wanted to but it has been put on hold and there is no short term plan to move to the cloud. Regards,

Just voted ... experienced this pain too many times so far!

Hi Ajay, Checklist doesn't currently support searching by status. This is something that we hope to deliver in a subsequent version.

Changing the original estimate mid sprint would surely affect the sprint burdown chart. Can't you just, using the log work link, enter the hours spent estimating the issue and restimating it to the number of hours it will take you? Of course the ideal curve on the burdown will not make in more sense but the burdown itself…

We did plan to offer a cloud based version but someone else released a similar version which is available on OnDemand instances. Therefore, we decided to postpone the development for a while ... maybe indefinitely. Sorry for the inconveniences.

Hi Miguel, The only items that you cannot be removed at the issue level are the one that have been created as options in the configuration page. Any item added in the issue itself can be removed by clicking on the pencil icon and removing the wanted item. Just delete the * and the text related to the item you want removed.…

Hi Sabine, There are no such options. Can you tell me which version of JIRA and Browser you are using?

Unfortunately, the current implementation does not listen for CTRL+Enter. I have added the suggestion to the backlog.

Hi Andrey, I saw the comment you left on the review. Just to let you know that an empty checklist will not appear at first on the issue details view until it has a value in it. That's the default behaviour that JIRA has implemented. However, you can click on the edit issue button and the field will be there. Then, once a…

Hi, When you say "hide", you mean the entire checklist or just items within it? Unfortunately, this is not something that can be natively done with checklist.

I am not necessarily answering the question asked here but it sounds strange to me that you would want to do that. I assume that the goal here is to make sure that stories are ready to be executed into a sprint? The Draft > Planned > In Progress > Done workflow sounds good for a KanBan where no sprints are defined but you…

I have sent it to the email address you left when purchasing the add-on. May it was spammed because of the attachment. I have sent you another email. If you don't receive anything still, contact me via the email on this page. Yves

Hi Helmut, Knut, I have sent you a beta version of the add-on to validate if it fixes the problem on your side. Yves

Hi Helmut, I will investigate the issue. Sorry for the inconvenience. Yves

Hi Helmut, Please try version 3.1.7. It should now be working. If not, please let me know and thank you very much for reporting the issue. Regards, Yves

Hi Helmut, Thanks for the additional info. I will investigate more and give you feedback. It seems that Atlassian changed how it dispatches its events in the new version. Hopefully I will be able to rehook the plugin properly. Yves