Jack Brickey Expert

BTW, I am current on mobile device making it difficult to set this up and test.

Why have a field required that has a default? If you test by not making it required does it resolve the issue?

So you only want to hide done sub-tasks if the parent story is done? What about for the exception case where the story is done but one or more sub-tasks are in progress? If your goal is to only hide the subtasks when the story is marked done I think you are going to need to consider adding a label to the subtasks once the…

I can't reproduce this. I would recommend two paths... * recreate the request type and retest * contact Atlassian Support 

Those are all normal default PFs.

I recommend creating a Quick filter (Custom filter) as I mentioned. The filter I would suggest would be - statusCategory != done

Thanks. Can you share the screenshot from the project settings > request types and the edit view of the form? I'm scratching my head on how this could occur TBH. Are you seeing this on other request types? It would be interesting to try to create a new request type to replicate.

Hi @Anna Arczynska , are you illustrating that the issue is created with the three fields left empty? Can you indicate the source of the screenshot? Is it from project setting > request types or somewhere else? What is the behavior if you use the Create button?

You can use Automation to accomplish this with one exception. You can’t prevent someone from editing the OE at least not natively. Below is a concept on the rule but I would need more details to get closer. You could actually create a manual rule to create your epic and tasks if desired. trigger - issue created condition -…

What I would do here is to create a new workflow from scratch and replace the existing one. 

To the best of my knowledge, there’s no way to just simply hide the field all together. Rather, you use a Context to hide all of the values in the sub field or simply use “none” as the only value in that context. 

Hi @Karthik Kaliki (EXTERNAL) , a few thoughts here... * check the history tab to assess any clues * check the workflow for any conditions or validators that might be on the transition into Done * Can you transition to Done from other statuses? If you transition into UAT and attempt into Done.

Can you not simply create a different Context for the field for the specific issue type? This is possible in Cloud and assume it would be there in Server.

Hi @Sandra Henriksson , I assume all of you're done issues are in the right most column where they belong. This is to ensure that the done issues are closed out properly when the sprint is completed. With that said hiding, these should only be a temporary action vs. removing from sprint. For this I recommend using a quick…

Hi @Tomasz Sarzyński , it is interesting that the number changed. What I previously set this up for a client. I had the client's Agents add the number to their smartphone phone book with an appropriate name. I have not heard of the number changing and feel it would be interesting to reach out to Atlassian customer support…

You should be able to expose the Priority and make optional on the Request. While it would be editable by the customer at the time of creation it really won't matter since it will be overwritten post-create. It won't be editable by the customer post-create.

Like the error indicates you should use a "Branch". Actually the link to the post that Walter provided below illustrates this. Give that a try and if you still have issues let me know. I created the following "untested" example for you. You probably should further qualify the JQL to restrict to your project to ensure you…

talk to your Jira admin and see about creating a unique scheme for your project or a unique workflow if that is the better option. Based on what you have conveyed here, it seems like you are sharing a workflow scheme, where that is not desirable.

Hi @Menaka , your date/time format is a system-wide configuration and can be modified by a Jira admin under administration - system - look and feel.

I am a bit perplexed as to why Bill's suggestion did not work unless there are two custom fields by the same name.

Hi @Eric Wieszczecinski , the answer depends on some details in your situation. Can you answer the following for me? * is this a Company managed project or Team managed project? Look in lower left corner for the answer. * is this a software or business project? Look in the upper left corner under the board name. If CMP…

Hi everyone! I'm late to the party here. I live on the east coast of US. My career has been in engineering and for the last 25 years I have been in various leadership roles mostly in product development and IT. I played around with agile development a bit prior to Jira but really Jira is what landed me there more…

Here is an old post - /take-jira-new-update-s-to-bugzilla Also check this out - bugzilla-connector-for-jira personally, I agree with Nic here, get users to settle on using Jira as a replacement.

If I'm off target let me know.

Hi @paul_creedy , an agent can add attachments to an existing issue in the following ways: * via email by attaching to the email reply to reporter * via the issue view by drag-drop into comment * by clicking on the Attachment icon in the issue view see if this article helps - attach-files-and-screenshots-to-issues 

👍

Hi @Yakov Melman , First off are you wanting to use the existing due date field or create a new one? If the latter, please be sure to use something other than "due date" since that is already a system field. Either way you should use automation to copy the date field. Below is what I think should work however I have not…

Hi @Devi Vaishnavie , assuming you are using CMP project here. Can you have a look at the JQL under Board settings/quick filters?

Hi @Ali Raza , I am confused by "I had already set the rule...". Do you have some automation rule involved here? If so please explain. If not what do you mean by rule? Based on your original post I thought that you were simply having problems where email responses to existing issues would occasionally result in new tickets…

Hi @Gregory James , Please try the following leaving off the ".name" Complaint Type: {{issue.COMPLAINT TYPE}} Customer: {{issue.Customer}} Non Conformity Type: {{issue.non conformity type}}