Jack Brickey Expert

Hi Jeff, I can't say how hard it is to change it personally. I guess it would depend on the requirements/solution. Should it be configurable and if so would it be a system config or per project. In any event this feedback is something that should be shared with Atlassian (feedback, JAC, Support).

I think the issue is with your malformed smart value. Move the"/60" outside of the braces. {{issue.Original estimate}}/60 The only other difference that I see is that it appears you have a global rule while mine is project specific but that shouldn't matter.

That was one of my theories in my first suggestion... can you verify that the trigger does not have the following checked? Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule. however, I wrongly assumed that was an option on the issue updated…

hi @Filip Novák , this quick test worked for me. Note, I used "60" to convert the OE from seconds to minutes.

If you wish to hide the issuetype you will need an addon app. If you happen to have Scriptrunner here is a reference on this topic - behaviours-restricting-issue-types 

Thanks Sebastian. I tested this very scenario just now and it works as expected, only one comment. Definitely something going on in your instance it appears. Keep me posted on what support I have to say.

quite odd for sure. I wonder if it is possible that you have some add on what is creating this conflict. I cannot reproduce it in my instance. Could you tell me what update you are performing on the issue that triggers the event so that I might test the same? Other ideas: * Test in another project * Contact Atlassian…

quite odd... can you try the rule illustrated?

another suggestion - simplify the rule as below...

Hi @Sebastian Pechhold , can you verify that the trigger does not have the following checked? Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule. Also please check that there are no other automation rules. One quick test would be to change…

So the Velocity report is good to show team performance over time. However, as you have noted does not based on a individual user. The only way to achieve that would be to have a board specific to each user. There are at on marketplace solutions, e.g individual-velocity-report-chart-gadget-for-jira or you could consider…

Hi @Lara Sousa , what performance report are you referring to? Is this an existing report in one of your projects? Can you provide a screenshot?

Hi @jyoti soratur , did you check any of the related posts show to the right under "Related Community content"? Also, you might use the Search box above, for example - https://community.atlassian.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&q=Integrate+with+nagios+ There are also apps in the…

Hi @Alisa , indeed, you would need to keep the file in a document management system/application. In a previous company, I worked at we used SharePoint for document management. We would then have links to these files if we needed to keep them updated.

What are the results of the 24 hour test?

Hi Andy, first I want to clarify that I do not work for Atlassian. I am just a user like yourself. Therefore, I cannot speak for Atlassian here. With that said, where exactly is your epic showing in the backlog? I checked a test project that I have and old done epics are not displayed anywhere that I could see. Maybe you…

@Michael Schreiyäck , I just wanted to check back in with you to see if you still need assistance.

Could you test user access on the SW project? Maybe you could do this with your user account first? * verify you can browse issue in the SW target project * Manually Create an issue in the SW project and verify that you can select your nam for Customer Sign Off * Assuming #1&2 are successful then try creating an issue in…

also if you use Business projects than you get a calendar view there as well.

What are your requirements? Here is what the marketplace shows - jira-free-calendar 

Hi @Mélanie Liguet , Why not have a unique workflow for the epic issue type and add a validator on the create transition restricting it to a specific user or group of users.

Hi @Kathryn Gerrell , I'm surprised it's only one field copy over given both are TMP. ;-) Joking aside, have you confirmed the user being copied from the JSM projects exists (has necessary permissions) in the SW project?

oh, and before I forget... The Epic will disappear from the drop down list on the Board view once the last child story/task is gone from the board. If memory serves Done issues disappear after 14d.

Hi @Andy Gritton (and all), This is a rather old post and TMP (PKA next-gen) projects have evolved greatly. I thought I would update this post with the latest behavior as indeed you can't hide done epics in the Roadmap view quite easily in TMP now. Below is an image that illustrates how this is done. Basically you click on…

A Form is associated with a Request Type. They have a 1:1 relationship. If you desire different forms the must be associated with different RT. With that said, there's no way to present different request types to different customers. All customers will see all request types associated with a given project portal.

Duplicate post

Ok. Let me know if the 24h deal works. I find it unfortunate that the issue was simply closed without some comment added as to why "won't fix".

Hi @Martin Warford , OOTB issues created by email are sent to a single email address which is associated with a single RT. You could consider using Automation to change the Issuetype/request type after the issue is created. Or you could consider using a custom field to further classify the issue.

Thanks for reporting the bug @Dennis Celen . Did you try the workaround?

@Deepak Rai , could you please share a JAC link to the known issue?