nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I set different default field values based on creator of the issue?

Zach Dimond

I would like for the manager of one board to be able to create a task in their backlog, and immediately have it visible there (and in no other backlog), with minimal extra work for them.

I have 4 different boards (with their own unique statuses) in the same project, representing 4 departments/stages in our SDLC (that is, epics from one board/dept flow into the next). However, each backlog has a manager who is creating tasks there, for that board (many times, breaking down the epic for the dept).

Since creating an issue can only give it one status, and I cannot create triggers on that “transition”, my workaround has been to have a required field on creation that says “dept” and then use a JQL filter to only show issues on any dept board that they pertain to. However, this is a time consuming issue creation method for them.

Is there a way to automate this process at all? (Assume I cannot create this in multiple projects, and cannot use different issue types)

Accepted answers

John Funk

Hi @Zach Dimond

Your best bet would be to use some type of Marketplace App like Automation for Jira or JMWE or ScriptRunner to accomplish that.

If you just use the custom field that you have already created for Dept, then use that value, that should work. What is so time consuming for the user to populate that one field?

All comments

John Funk

Hi @Zach Dimond

Your best bet would be to use some type of Marketplace App like Automation for Jira or JMWE or ScriptRunner to accomplish that.

If you just use the custom field that you have already created for Dept, then use that value, that should work. What is so time consuming for the user to populate that one field?

Zach Dimond

It's just two extra clicks for them, so when they are breaking down an epic/adding tasks en masse, it just gets to be a bit of an annoyance, nothing more. Thank you for the answer!

Ravi Sagar _Sparxsys_

Hi @John Funk @Zach Dimond

Why not add a query based on reporter in your JQL to differentiate based on the person creating the issues?

Something like this.

reporter in (manager1, manager2)

or this in case reporter is changed in future.

reporter was in (manager1, manager2)

This is probably simpler way of doing it provided you can manage the list of managers in the JQL. You can also use group name in the JQL like.

reporter in membersOf("manager-group")

What do you think?

Ravi

Zach Dimond

I think that's a great idea, and one we've considered, but I think it might be difficult if someone has to cover another person's work in the case of vacation, absence etc.

John Funk

In that case, you should probably capture the value for the Dept field in the Epic and then let the tool copy that value down to the individual stories/issues.

John Funk

Well, one note is that the Reporter field is updatable - in other words, if someone is creating an issue for another person, just change the name of the reporter while the issue is getting created. Or like I said above, base it on the value of the Epic.

Zach Dimond

Thank you, John, this is a complete and satisfactory answer. Appreciate it!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud